Various binaries are available for 32-bit and 64-bit Windows, and also  for OSX using the Carbon and Cocoa APIs, for Python 2.5, 2.6 and 2.7. And source code is also available at http://wxpython.org/download.php of course, for building your own.

• Changes in 2.8.9.2
  
• Download (source, Windows and Mac binaries)
• APT (Debian or Ubuntu packages)

• Changes in 2.8.8.1
  
• Download (source, Windows and Mac binaries)
• APT (Debian or Ubuntu packages)

• Changes in 2.8.8.0
  
• Download (source, Windows and Mac binaries)
• APT (Debian or Ubuntu packages)

NOTE: On Mac OS X 10.5 (Leopard) the Python 2.5 binaries of wxPython expect to be used with the user-installed version of MacPython, not the Apple installed version. A fix for this issue is being worked on for the next release. In the meantime you can either install MacPython 2.5.1 and adjust your paths so that that Python is used, or you can stick with Apple's Python and the wxPython 2.8.4.0 that comes with Leopard.

Happy Hacking!

An interesting thing about this release is that I made the build, uploaded about a gig's worth of installers and packages, and everything else that goes into making a release, all while being out of town and away from the machines doing all the work. I was able to make all the final tests and adjustments on my new Mac, using VMware Fusion for the Windows and Linux specific work, and then used Mercurial over an ssh tunnel to push my changes back home to my master build and release machine. The next part was easy, since I have been doing mostly automated builds for a few years now. I just start it going via a ssh login and then checked on it a few hours later from the hotel to see if it's done. At that point things started to get a little tricky, mainly because I usually do the rest of the release process by hand and in person. Since the full build is about a gigabyte of binaries I transfered just a few of them to my local machine for testing, and then I had to deal with uploading remotely from the build machine to SourceForge and our APT repository, all while I had a flaky wireless connection here and while attending various meetings. Then I realized that the software I usually use for editing the website is only installed on a machine at home. Well anyway, I muddled through and managed to get it done, and now I know where my release process could use a bit more streamlining and automation...

The upside is that some of the things fixed and polished in wxWidgets would have been problematic for some wxPython users, and so we'll skip those problems and not have to deal with them at all. (Some were bugs introduced by the fixes for other bugs, so you may not notice any changes at all compared to 2.8.4.2, other than the original fix.) The other upside of this skip is that all of the usual last-minute distribution related problems have already been worked out while I was working on doing a 2.8.5.0 build, and that should allow me to have the 2.8.6.0 build ready fairly soon after the wxWidgets release (or maybe even before if they wait a few days for the announcement like they've been doing lately.)

The downside is that I'm going to be on-site at OSAF all of next week celebrating the release of Chandler and planning Chandler's next steps, so I will likely be running this release build remotely. I guess I'll get a chance to see exactly where all of the holes in my automated build system really are!

Anyway, the preview build is in progress right now. If you're interested in testing or in having the bleeding-edge version of the binaries then keep an eye on the wxPython-dev mail list for an announcement from R'bot when he is done with the build and upload.