On 16/12/2010 10:58, Rafael Villar Burke (Pachi) wrote: > Thanks Dieter. I hope this helps the original poster. > > Another issue is, can pygobject on win32 be fixed to be more backwards > compatible like in this scenario?
Good question. There's a tiny little detail to consider though: There are no binary compatibility guarantees whatsoever for the GTK+ binaries provided on ftp.gnome.org. There was a message once by Tor Lillqvist (if I remember correctly) on some mailing list where he stated that (but I can't seem to find it). If that still holds, there seems to be no use in getting newer PyGTK/PyGObject/* versions working with ancient GTK+ releases on windows. You could maybe fix this specific case, knowing more trouble can and probably will be discovered in the future... After some more pondering, the "solutions" I proposed in my previous message are not fully correct either. The only real solution for this case would be for Gimp to package it's own Python interpreter (like the Gedit windows installer does) with it's own PyGTK-2.16/PyGObject/etc and make Python-Fu use that instead. In other words, make Gimp a fully self contained package with regards to it's Python support. It's not that wild an idea either, asking Gimp users to install Python/PyGTK/etc to get Gimp plugins working is like asking Notepad users to install visual studio to get basic macro's working. I know, it's a bad analogy, but what I'm trying to say is that the Python/PyGTK/etc installers should probably be considered development tools and should not be part of any gtk+/gnome platform/whatever- you-want-to-name-it based end user package. mvg, Dieter _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
