Some words about versioning.
In one of the wxPython 2.5 releases (I do not remember which one exactly), Robin introduced the wxversion module and the installation of multiple wxPython versions. All this based on the Major.Minor.Release number, eg 2.5.1, 2.5.6 and so one. This was really great, we could
have different wxPython versions installed.
There was a small issue. The versioning scheme could not differentiate correctly the ansi/unicode version. I spend a lot of time to improve and fix this issue (See mails exchanges somewhere in the wxPython-dev list)
Finally, a new wxversion module was born. It was able to select a version based on the Major.Minor.Release and the chartpye, ansi/unicode. So far, so good. I updated all my applications.
When the first 2.6 version arrived (2.6.0), I noticed the wx.pth contained only the the Major and Minor numbers. The release number
was dropped. The installer (at least for the win platform) was modified accordingly. I quickly proposed Robin to change this, thinking it was
an error. It was not, see
http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?11:msp:39775:fflhmkmhfilinbdimeok
I suspected future problems and once again, I changed my developing strategy. I decided to freeze all my applications with py2exe. All the libs are statically linked. Since then, I have no problem. A side
effect of this is that my apps are no more available as scripts.
Now it seems, the wxversion hell is starting again.
Jean-Michel Fauth, Switzerland.