RSS/Atom feed Twitter
Site is read-only, email is disabled

GIMP and Python

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 6 messages available
Toggle history

Please log in to manage your subscriptions.

31958730.1126080.1271291202... Michael Hansen 15 Apr 02:26
  201004151028.19465.tneuer@i... Torsten Neuer 15 Apr 10:28
   GIMP and Python Alexia Death 15 Apr 10:48
   GIMP and Python Tor Lillqvist 15 Apr 11:33
    201004151237.24015.tneuer@i... Torsten Neuer 15 Apr 12:37
  GIMP and Python Jernej Simon?i? 15 Apr 11:34
Alexia Death
2010-04-15 10:48:07 UTC (over 14 years ago)

GIMP and Python

On Thu, Apr 15, 2010 at 11:28 AM, Torsten Neuer wrote:

Am Donnerstag, 15. April 2010 02:26:42 schrieb Michael Hansen:

And my second question: If this is really the case, will establishing  Python support be simplified in future (by embedding native support for  Python scripts)? OpenOffice or the newest version of Blender already come  with all necessary files to use Python scripts for example, without the  need to install all that stuff.

It seems that you're talking Windows in this case. ;-)

Frankly, it is a very bad thing when applications include a script language engine in their distribution that then is installed somewhere in a non- standard place on the platform.

This is windows we are talking about here. Nothing that isn't provided by MS$ has a standard place in the OS. Its nature deems that for your things to work you need to provide all your own dependencies. And yes, that means potentially 6 copies of python, GTK or any other dependency. It is regrettable, but treating windows like a Unix system is just as wrong. Windows is not a version fixed and built as one environment. What works for one app does not have to work for another because they can have totally incompatible versions. There was a time when applications did not package their own GTK. It was a pain in the ass to figure out why gimp install broke pidgin. Yes, it bloats windows, but it ensures that apps run OK for those that lack the skills to resolve conflicts.

Tor Lillqvist
2010-04-15 11:33:42 UTC (over 14 years ago)

GIMP and Python

It seems that you're talking Windows in this case. ;-)

Frankly, it is a very bad thing when applications include a script language engine in their distribution that then is installed somewhere in a non- standard place on the platform.

But what is the "standard" place for Python on Windows? And are you sure that some version of OpenOffice.org for instance even would work with whatever Python version the python.org people currently consider "standard"?

On systems with package management and svendor package repositories that *do* offer standard packages of everything imagineable in the FLOSS worls, the situation is quite different of course.

--tml

Jernej Simon?i?
2010-04-15 11:34:34 UTC (over 14 years ago)

GIMP and Python

On Thursday, April 15, 2010, 2:26:42, Michael Hansen wrote:

And my second question: If this is really the case, will establishing Python support be simplified in future (by embedding native support for Python scripts)?

GIMP 2.8 will optionally include Python and PyGTK+ on Windows.