Introduction

In the begining there was Python, and Python had modules, and Python was good. But after a time Guido looked on Python and saw that Python needed organizational assistance, and so Guido took code from Python's @@ -69,8 +351,8 @@ have concerning the new wx package. Please also take a look at the 2.5 Migration Guide to see notes about other big differences in this release.

Why change anything?

This change is being made for a couple of reasons. The first reason is to discourage the use of import *, which is a dangerous technique that can create name conflicts and bloated namespaces.

@@ -93,8 +375,8 @@ class Frame(wx.Frame) the same thing (implement a new wx namespace and drop the "wx" prefix) and we want wxPython to lead the way.

What does the new wx package do?

As mentioned in the Introduction, wxPython 2.4.1 introduced a way of getting to this new syntax as quickly as possible. It would import the old names (like "wxFrame") from the old package and then create new @@ -108,8 +390,8 @@ populated with modules that simply import the new names and then complicated, but it is mostly automated and so it doesn't cause problems in most cases.

Will any of this effect my existing code?

No. Your existing code will continue to work and be supported for some time. It will be up to you to decide when to switch to the new syntax. But all new documentation and code examples will use the new @@ -123,24 +405,24 @@ old code is depending on some of the implemtation details, or if you are using other things that have changed in the API. See the Migration Guide for more details.

What about all the other modules, like grid, html, and stc?

There's more to the old wxPython than just the wxPython.wx module. And we've got those extra modules covered as well. Each of those modules (as well as the lib subpackage) has been moved to the new wx package and reverse-renamers have been placed in the wxPython package as needed.

How do I use this new wx package?

The wx package is automatically created when you install wxPython version 2.4.1 or higher. So all you have to do is:

 import wx

What are the issues with converting old code to use the new wx package?

Obviously, you need to change your import statements from:

 from wxPython import wx
@@ -161,8 +443,8 @@ class MyFrame(wx.Frame):
 In most cases, existing code can be modified with a simple search and
 replace.

Where can I find example programs using the new wx syntax?

The wxPython demo application and most of the sample apps have been converted to use the new import wx style of programming with wxPython, so there are lots of examples to look at and to play with.