You are here

Python-fu installation failed miserably - HELP!

For one of the many usual reasons, I had to wipe my c:\ hard drive and re-install Vista Home Premium and all my software.

Specifically, I followed the directions in to get Python-Fu working again -- NOT!

The first recommended step is to get Python 2.6. The hot link from the above page to vectors you to the Python 2.6.7 page whence you can get ONLY the source code for the latest revision of Python 2.6. Well I don't know how to compile C++ code but I did search Google for "Python 2.6" and found which allowed me to download python-2.6.6.msi which seemed to install Python in c:\Phthon26.

Going back to the GimpUsers tutorial, I next hotlinked to PyGTK Downloads at and tried to install the recommended all-in-one installer: pygtk-all-in-one-2.24.0.win32-py2.6.msi. Alas, it bombed out because something that whomever put the installer package together was supposed to set in some table somewhere, TARGETDIR, was somehow wonky. Well, that was way over my pay-grade so I fell back on getting PyGTK, PyCairo, and PyGObject from: - pygtk-2.24.0.win32-py2.6.exe - pycairo-1.8.10.win32-py2.6.exe - pygobject-2.8.3.win32-py2.6.exe

They installed just fine. Then I re-installed GIMP as per the tutorial. But when I tried to run GIMP, I got a zillion error messages, all saying that "The procedure entry point g_malloc_n could not be located in the dynamic link library libglib-2.0.0.dll." followed by Microsoft Windows saying that "unsharp-mask.exe has stopped working." Followed by the same error message for softglow.exe, etc., etc. I gave up and used Task Manager to shut down the GIMP installer.

I suspect I am in the well-known "DLL hell." Firstly it is my dim understanding that some DLLs do not, in fact, contain executable code and contain, instead, just "pointers" to who-knows-what, who-knows-where. Secondly, as DLLs got updated by who-knows-whom, this or that program, that used a common DLL, needed this or that prior revision of the DLL -- which turned out to be a huge mess (hence the term "DLL hell"). Which problem was "cured" in Vista by simply saving EVERY version of EVERYTHING in a huge hidden file.

The Python people are up to version 3.7 or so and we GIMPers are still using version 2.6. I tried as hard as I could to get all the right versions of Python, PyGTK, PyCairo, and PyGOject. Python-fu usta-did-work for me before my re-install. Can anybody tell me where I went wrong and what I should install instead of the above and/or what to do about the DLL(s) in the error message? HELP!

I could run down a list of possible suspects, but it never meshes for "everyone" because each user has a different OS or method of doing things, much like your case.

I've ranted on this issue over the last couple of years because, although Python seems to be wonky when Windows is involved, it seems to hit and miss with people using the same OS using the same set of instructions. So, I want to point out a thread that is currently ongoing at GIMP Chat, where Rod is trying to help Molly get Python installed. You can read the entire thread and see if you can glean something from it and hopefully get your Python working again for GIMP.

The Python portion of this thread starts here:

A possible explanation of your problem is that the stable version of GIMP (2.6) is many years old. You have to remember that only bug correction goes in on stable version and the version of the files you tried are recent so they are probably for the experimental one (2.7).

I would try 'pygtk-2.12.x', 'pygobject-2.14.x' and 'pycairo-1.4.x'; where 'x' is the highest number you find. Those versions are contemporary to the beginning of GIMP 2.6. As for the Python interpreter, keeping 'python-2.6.6.msi' make sense (GIMP will accept it) even if part in the name of the above file is '...-py2.5...'. After having a functioning Python in GIMP, perhaps you should install 'glade' also (but don't know the version), as a few Python scripts use that.

Hope this help you a little.
"Expressing myself in English is a battle I never win"

To make your life easier you may try this (for 32 bit )
or at 64 bit

It is not the stable but one of the last 2.7.x dev version, seems quite stable , PYTHON is pre installed so WILL WORK OUT OF THE BOX, and since is portable will not interfere with other Gimp, in case you want use also the stable version

and already include some of future 2.8 improvements :
as option for single window mode, improved brush tools,layer groups..

Subscribe to Comments for "Python-fu installation failed miserably - HELP!"