The wxWindows project and library is now known as +wxWidgets. Please see here for more details.
+This won't really affect wxPython all that much, other than the fact +that the wxwindows.org domain name will be changing to wxwidgets.org, +so mail list, CVS, and etc. addresses will be changing. We're going +to try and smooth the transition as much as possible, but I wanted you +all to be aware of this change if you run into any issues.
+The import-startup-bootstrap process employed by wxPython was changed @@ -31,7 +41,7 @@ potential problems are that the C++ side of the "stock-objects" (wx.BLUE_PEN, wx.TheColourDatabase, etc.) are not initialized until the wx.App object is created, so you should not use them until after you have created your wx.App object. If you do then an exception will -be raised telling you that the C++ object has not bene initialized +be raised telling you that the C++ object has not been initialized yet.
Also, you will probably not be able to do any kind of GUI or bitmap operation unless you first have created an app object, (even on @@ -109,7 +119,8 @@ automatically generate a new ID if -1 is given, similar to using -1 with window classess. This means that you can create menu or toolbar items and event bindings without having to predefine a unique menu ID, although you still can use IDs just like before if you want. For -example, these are all equivallent other than ID values:
+example, these are all equivallent other than their specific ID +values:1. item = menu.Append(-1, "E&xit", "Terminate the App") @@ -393,7 +404,7 @@ different API.