I developed an application using wxPython 2.8.7.1 and Python 2.4. When I
tried to run it on a different machine that had wxPython 2.8.7.1 and
Python 2.5, I discovered an incompatibility with Python 2.5, which I
have since solved (nothing to do with wxPython).
On two of three machines with this problem (Ubuntu 7.10, Kubuntu 7.10)
installing Python 2.4 from the Ubuntu repositories solved the problem.
However, on the third machine, also Kubuntu 7.10, Python 2.4 installed
fine, but my program complained that it couldn't import wx. I opened up
a Python command shell and typed 'import wx' and got the same error. I
solved the problem by copying the wx-2.8-gtk2-unicode directories from
the Python 2.5 site-packages to the Python 2.4 site-packages.
I believe that in all cases wxPython was installed from the
http://apt.wxwidgets.org repository.
On the machines where wxPython automatically installed itself with the
new installation of Python 2.4, it looks like wxPython was installed
from a Python egg. I'm guessing that on the other machine (I don't have
access to it right now), it wasn't.
Questions:
Was there a change to the wxwidgets.org repositories to switch to
the .egg format?
Does the .egg format automatically adapt itself to new Python
installations?
When I looked at the one machine where I definitely know the order of
installation: installed Python 2.5 as part of installing Ubuntu Gutsy
(7.10), then I installed wxPython from the repository. Later, I
installed Python 2.4 from the Ubuntu repository. It looks like in both
Python site-packages directories, most of the wxPython install contains
links to files in /usr/lib/pycentral.