I've done a bit more work on this since the last message. To summarize
I now know how to fix the problem with not being able to derive from
object, but that uncovers another problem that I don't know how to fix yet.
There will definitly be a fix for this in the 2.5 series with the switch
over to the newer swig as all the wxPython classes will then be
new-style themselves. If there is time I'll still try to find a
solution for 2.4.2 also.
···
--- Tom Ayerst <twa@post.com> wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I've done a bit more work on this since the last message. To summarize
I now know how to fix the problem with not being able to derive from
object, but that uncovers another problem that I don't know how to fix yet.
There will definitly be a fix for this in the 2.5 series with the switch
over to the newer swig as all the wxPython classes will then be
new-style themselves. If there is time I'll still try to find a
solution for 2.4.2 also.
Thank you very much for the info.
I suspect I should know this but; where can I find the timescales for the next release?
The wxWindows team hasn't always been very good about sticking to schedules in the past but there is a new roadmap on the website and also some external influences (more info by the end of the month) that will help us stick to the schedule:
Normally the wxPython releases follow the wxWindows release by a week or two, although since I am making some big changes in 2.5 that time gap will likely be larger for the first 2.5.x wxPython.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!