Dave Aitel wrote:
I've been using the latest pygtk 2.4 from the win32 distro site - I've been testing Python 2.4, which is when the crashes started. pyGTK is the only binary module we import, so I'm assuming it's pyGTK, although I don't have proof, and a stack trace didn't seem very interesting.
Two things come to mind:
* pygtk uses the PyGIL api calls when built w/ python 2.4. This should be an improvement, but it is a different code path.
* python 2.4 uses the msvc 7.1 C runtime dll and gtk uses the msvc 6 runtime dll, which may cause problems.
Note that PyGTK 2.4.1 does *not* use the PyGIL calls because of a bug in pygobject.h. It checks for Python 2.4.0a4 or greater using the PY_HEXVERSION constant, which is actually not defined. It should PY_VERSION_HEX instead. This was fixed after PyGTK 2.4.1 was released.
I'm using PyGTK 2.4.1 with a patched pygobject.h and version of Python 2.4 that I compiled using MSVC 6 and it works fine for me.
-- Tim Evans Applied Research Associates NZ http://www.aranz.com/ _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
