migration guide obsolete modules suggestion

There is a sentence in the "Other Stuff" section of the Migration Guide that
isn't explicit enough.

"Instead of over a dozen separate extension modules linked together into a
single extension module, the "core" module is now just a few extensions that
are linked independently, and then merged together later into the main
namespace via Python code."

I just had someone ask we why his code broke and it turned out he had been
using.

from wxPython import events

That is one of the modules that got axed in 2.5.1.5 AFAIK. So, I suggested
explicitly listing the "dozen separate extension modules" so that it is
clear which ones are now part of the wx namespace even if you're still using

from wxPython import wx

or

from wxPython.wx import *

ka

Kevin Altis wrote:

That is one of the modules that got axed in 2.5.1.5 AFAIK. So, I suggested
explicitly listing the "dozen separate extension modules" so that it is
clear which ones are now part of the wx namespace

Done. I've also recently changed the name of the core namespace submodules to have a leading underscore which should help give clues to the programmer that they are private implementation details.

ยทยทยท

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!