Tentative wxPython Roadmap
This page describes a very tentative, high-level, loosey-goosey, pie-in-the-sky roadmap for wxPython. You may notice that, other than the date the document was last updated, there are no dates specified. This is because it has been my experience that assigning dates to milestones in an open source project almost never results in the dates actually being met. So instead I'll use tags like "soon", "future", etc. to describe the general intent of when the items will be accomplished, and I'll keep the items more or less in the order that I think that they will be accomplished.
This roadmap describes what is planned for future work on wxPython as of 19-April-2011.
2.8.11.0 release: (completed)
2.9.1.1 release: (completed)
OS X Cocoa build: (completed) The 2.9.1.1 release included a Cocoa build for Mac. While it still has some rough edges and some unimplemented corners, it is very usable. For some things the Carbon build may still be a better choice. Be sure to test your application with both and decide which is better for you. It is expected that as time goes on the Cocoa builds will continue to get better and will eventually surpass the quality and abilities of the Carbon build, which will eventually be phased out.
OS X 64-bit build: (completed) The Cocoa build in the 2.9.1.1 release includes a 64-bit architecture in the fat binaries. The binaries in the Cocoa builds now include the PPC, i386 and x86_64 architectures, and are expected to be compatible with OSX 10.5 and beyond. (There was a bug in the 2.9.1.1 build scripts that prevented compatibility with 10.5 but that has been resolved.)
2.8.12.0 release: (completed) This is pretty much a big-fix only release, although some of the 3rd party modules in wx.lib have also been updated and include some new features.
2.9.2.x: (soon) Building 2.9.2 previews is my next major task, so everything will be ready when the wx team is ready to officially release 2.9.2. It is expected that the 2.9.2 previews will be in better shape than the 2.9.1.1 release in many ways so if you are using 2.9.1.1 you may want to consider switching to 2.9.2 as soon as possible (even if it is not officially released yet.)
wxPython "Next Generation": (ongoing) There has been some discussions off and on over the past couple years about a whole new way to generate the code used for the wxPython extension modules (a.k.a the C++ wrapper code). There has been some design work done towards this goal, and a proof of concept has been implemented. In a nutshell the proof of concept has exceeded all my expectations and I feel that this will be an excellent way to automate much more of the generation of the wrapper code. More information about the goals and design of the new wxPython can be found at ProjectPhoenix, and the source code can be viewed in the wx repository. Although the new approach will make maintenance of wxPython much simpler in the future, it is still a lot of work to make the transition and so it will not become the highest priority task until more of the low-level foundational pieces are completed and verified. In the meantime the current 2.9.x ReleaseSeries will continue to progress using the old technology.
Python 3.x support: (unknown) It is expected that some things being done for the Next Generation project will make it easier to be able to maintain support for both Python 2.x and 3.x in the same source tree, so I've been delaying putting much effort into a Python 3.x port in order to prevent wasting time on something that may end up getting thrown away once the NG switch is made. If that Next Generation project ends up being left on-hold for too long however then I'll probably revisit this item and move up the priority.