gimp scripting support

gimp scripting support

[Federico Beffa]

Hi,

I've updated the gimp in my profile and get the following errors:

Gtk-Message: Failed to load module "canberra-gtk-module"
Traceback (most recent call last):
  File "/gnu/store/9gnpd0vkwyvy6x7jiv1kjjdgf6gd1hjl-gimp-2.8.14/lib/gimp/2.0/plug-ins/gradients-save-as-css.py",
line 25, in <module>
    from gimpfu import *
  File "/gnu/store/9gnpd0vkwyvy6x7jiv1kjjdgf6gd1hjl-gimp-2.8.14/lib/gimp/2.0/python/gimpfu.py",
line 76, in <module>
    import gimp
ImportError: could not import pygtk


Given that 'pygtk' is now necessary, IMO it should be a propagated input.

Also, installing pygtk in my profile is not enough. This is because I
do use python-3, while gimp uses python-2. For this reason PYTHONPATH
doesn't work with gimp and I can't change it.

One solution is to define PYTHONPATH in a wrapper around gimp.

Regards,
Fede

Re: gimp scripting support

[Andreas Enge]

On Sat, Aug 01, 2015 at 06:01:19PM +0200, Federico Beffa wrote:
> Also, installing pygtk in my profile is not enough. This is because I
> do use python-3, while gimp uses python-2. For this reason PYTHONPATH
> doesn't work with gimp and I can't change it.

Could gimp be built with python 3?

Andreas

Re: gimp scripting support

[Federico Beffa]

On Sat, Aug 1, 2015 at 9:25 PM, Andreas Enge <andreas@enge.fr> wrote:
> On Sat, Aug 01, 2015 at 06:01:19PM +0200, Federico Beffa wrote:
>> Also, installing pygtk in my profile is not enough. This is because I
>> do use python-3, while gimp uses python-2. For this reason PYTHONPATH
>> doesn't work with gimp and I can't change it.
>
> Could gimp be built with python 3?

Actually making pygtk a propagated-input is probably not necessary and
should better be avoided...

Building with Python 3 doesn't really solve the problem, because if
somebody chooses to use Python 2 in his profile then it would have a
similar problem.

Fede

Re: gimp scripting support

[Andreas Enge]

On Sat, Aug 01, 2015 at 10:12:02PM +0200, Federico Beffa wrote:
> Building with Python 3 doesn't really solve the problem, because if
> somebody chooses to use Python 2 in his profile then it would have a
> similar problem.

I know, but at least it would tend to favour modernism :-)

Andreas

Re: gimp scripting support

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> On Sat, Aug 01, 2015 at 06:01:19PM +0200, Federico Beffa wrote:
>> Also, installing pygtk in my profile is not enough. This is because I
>> do use python-3, while gimp uses python-2. For this reason PYTHONPATH
>> doesn't work with gimp and I can't change it.
>
> Could gimp be built with python 3?

Speaking of which, there’s something funny to investigate:

--8<---------------cut here---------------start------------->8---
$ guix size gimp
store item                                                       total    self
/gnu/store/bk929m5h0h7rh1isk6zr4zv707gjg1kd-gimp-2.8.14            712.5    68.3   9.6%
/gnu/store/h73zg9bbgc91v6c9kb2694y6685cqyji-gtk+-2.24.28           548.3    35.6   5.0%
/gnu/store/6mdkf8ryzs6k61kl4jhphz5r920ximvp-cups-2.0.3             343.6    12.1   1.7%
/gnu/store/6sw6jp3hyld0zah16kdvpppfjwi5k27d-cups-filters-1.0.71    328.2     2.8   0.4%
/gnu/store/v0l3a5da32cmrd7l5lhrh9c5vlz7vmn3-python-wrapper-3.4.3   265.0     0.0   0.0%
/gnu/store/9iannnxg7mfnz6misi4nf1q8avdjrlzr-python-3.4.3           265.0    96.2  13.5%
/gnu/store/qlf4k2b81wms6avlyny7hix175asg8kg-python-2.7.10          245.9    77.2  10.8%
--8<---------------cut here---------------end--------------->8---

The two Pythons end up being pulled, uh!

Ludo’.

Re: gimp scripting support

[Ludovic Courtès]

Federico Beffa <beffa@ieee.org> skribis:

> Given that 'pygtk' is now necessary, IMO it should be a propagated input.
>
> Also, installing pygtk in my profile is not enough. This is because I
> do use python-3, while gimp uses python-2. For this reason PYTHONPATH
> doesn't work with gimp and I can't change it.
>
> One solution is to define PYTHONPATH in a wrapper around gimp.

Making a wrapper sounds better to me than using propagated inputs (it’s
less intrusive because it doesn’t pull new stuff in the user’s profile.)

Can you prepare a patch for this?

Thanks,
Ludo’.

Re: gimp scripting support

[Federico Beffa]

On Tue, Aug 18, 2015 at 5:40 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Federico Beffa <beffa@ieee.org> skribis:
>
>> Given that 'pygtk' is now necessary, IMO it should be a propagated input.
>>
>> Also, installing pygtk in my profile is not enough. This is because I
>> do use python-3, while gimp uses python-2. For this reason PYTHONPATH
>> doesn't work with gimp and I can't change it.
>>
>> One solution is to define PYTHONPATH in a wrapper around gimp.
>
> Making a wrapper sounds better to me than using propagated inputs (it’s
> less intrusive because it doesn’t pull new stuff in the user’s profile.)

I tried defining PYTHONPATH on the command line on which I launch
gimp, but it doesn't work. It looks like there's more than this going
on.

Regards,
Fede