Chris Barker wrote:
Robin Dunn wrote:
Is it possible that the python you used for running setup.py is different than the python you used to do the import shown above?
Anything is possible! Now that I've thought about it, very possible. I first tried building with python2.3, then with 2.4. The old libs may have been around, and didn't get re-built with 2.4. I had a hard time figuring out what to clean out to make sure it all gets rebuilt. with simpler dist-utils packages, there is a simple "build" dir to remove. What you should I remove here?
As you've probably seen wxPython's setup.py may add a 'gtk2' and/or a 'unicode' to the end of the build dir name in order to have the ability to switch between the kinds of build without having to rebuild the whole thing. But each build is still mostly self-contained in these build* dirs so to do a clean you can just remove build* and also the .so files. I've also put a custom clean command in setup.py that will take a out a few other files, but unless you are wanting to get back to a (nearly) pristine source tree then you don't really need to use it.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!