Just recently got 2.5.1 up and running on my laptap (Compaq Presario 710US
-- a 1.2 Ghz Duron thingy), Mandrake 9.2 distro, Python 2.3.3.
In general, things are working quite well, including the Cube and Cone demos
(I have PyOpenGL installed).
A couple of random feedbacks:
1) On the demo, the constrained new numeric fields (MaskedNumCtrl) fight me
when I try to enter a maximum value (check-box enabled). Just typing a
number in the max value blank generates weird behavior (especially trying to
interpolate a new digit). After a delay, the thing turns yellow, and with
little additional effort, causes the whole demo to die (it just disappears
off the screen).
I've also seen this with Will's new code that he recently sent me, I sent him some tracebacks last night. It looks like it is getting into some sort of endless (until final failue) recursion problem...
the initial examples pass a frame id of -1, but there's a -4 hard coded in
the class __init__ for some reason (i.e. the passed -1 is ignored), and this
causes a failure in one of the asserts (-4 is not legal). If I replace the
-4 with id (the passed parameter), then all is as it should be.
Thanks. Anybody care to volunteer to go through the wiki fixing any 2.5 compatibility issues?
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I recommend bringing this up on wxPython-users instead to get a larger population of people that can attack the problem. Also, given the instability of the wxPython 2.5.x API until 2.6 is released I think it would be preferable to just make a note on the page or as a comment in code the changes required for wxPython 2.5.x. If a special wiki name like WxPython25Migration is used then it might simplify revisiting those pages as things change and allow migration comments to be centralized and user-editable.
It seems like a bad idea to update the entire wiki to only use 2.5 code when 2.4.2.4 is the stable version. When 2.6 is released then I have no problem with everything getting changed to reflect that API.
Of course, I'm living on the bleeding edge and even forcing anyone that wants to use PythonCard 0.8 or later to ride the wxPython 2.5.x wave, but I don't think that is going to be generally acceptable to most of your audience. That is one reason I recommended that projects like wxGlade, wxDesigner, and Boa simply fork their code and have an "unstable" version to chase 2.5.x, use the new namespace, etc. Trying to support the old and new simultaneously is a royal pain. Whether they want to continue to do bug fixes or feature updates for the old 2.4.x stuff is up to them
ka
···
On Apr 16, 2004, at 10:33 AM, Robin Dunn wrote:
Kirby Urner wrote:
2) In the Wiki geared for teaching wxPython, http://wiki.wxpython.org/index.cgi/Getting_20Started
6.2.1, 6.2.2 etc.
the initial examples pass a frame id of -1, but there's a -4 hard coded in
the class __init__ for some reason (i.e. the passed -1 is ignored), and this
causes a failure in one of the asserts (-4 is not legal). If I replace the
-4 with id (the passed parameter), then all is as it should be.
Thanks. Anybody care to volunteer to go through the wiki fixing any 2.5 compatibility issues?
It seems like a bad idea to update the entire wiki to only use 2.5 code
when 2.4.2.4 is the stable version. When 2.6 is released then I have no
problem with everything getting changed to reflect that API.
This makes some sense. The Wiki is currently written for 2.2.5, not 2.4.x.
As a newbie, I don't find it prominently indicated that 2.odd are considered
"development versions" ala Linux. Only some versioning schemes assume that
convention. Python, notably, does not. So it's news to me that 2.6 will be
the next stable version.
