Hi,
In less than three days, I detected three issues in the new wxPython flavour,
and I am an amateur. I'm a little bit sorry for having reopened the wxversion
debate.
To my previous post (about wxversion.require), Robin Dunn replied:
That is by design. It is meant to be used only once, at the very
begining of an application.
When I read it, the answer became quite clear to me (and logical). I have
to select the the wx-version at the start of an application. Unfortunatelly,
I have my own lib, some modules of that lib have an import wx
statement, they do not knew anything about the wx-version. Naively,
and just naturally, I thought it would be a good idea to inform these modules
which version they have to use.
At the present state I see the situation like this.
1) I use import wx everywhere as I was just doing up to now, just
having a more bloated site-package directory.
2) If I use this new feature, once again I have to update
my lib in the same way I updated my lib to a new wxPython
version. I do not see how I can update my lib for a future non existing
version. Beside this, informing these modules about the version to
use is bad, version mixing and ...)
In both variants, the versioning mechanism does not bring something
interesting.
What to do? I do not know. I have just the feeling, wxPython
takes the wrong way. Thinks are happening to fast, there are too
many changes and structural changes in every version. A newer
version has new widgets and bugs fixes, but also bugs in new widgets
and incompatibilites.
I think, from an end user point of view, what wxPython needs is some
stabilization. Versioning must be re-thought, if it has been once deeply
thought. Arguments like, we have introduced versioning, but do not
use it if you plan to create windows executable, are not serious.
This applies to the "management" of wxPython, not to the lib itself.
After 2 (?) years of wxPython use, it seems the development is more
based on a trial and error process, than on a deep thinking. In one
sense it is not normal that such attentions are coming from end user
like me.
I french, we say something like "hunting to many hares at the some
time".
I will add, that I'm very happy with the actual 2.5.2.8 version. It looks
stable, it is what a final wxPython 2.5.0.0 should have been.
Regards.
Jean-Michel Fauth, Switzerland