import wx?

wxPython Users
1

Hi all,

Should I use " import wx" or " from wxPython.wx import *" ?
I am kind of confused here. I started using "import wx" recently and changed everything in my programm to work this way. Somthing like " wxPoint => wx.Point".
However, in most Demo codes I see using "from wxPython.wx import *".
So, what I should use do?

Thanks

2

Should I use " import wx" or " from wxPython.wx import *" ?
I am kind of confused here. I started using "import wx" recently and
changed everything in my programm to work this way. Somthing like "
wxPoint => wx.Point".
However, in most Demo codes I see using "from wxPython.wx import *".
So, what I should use do?

Theoretically, "from wxPython import *" will work in V2.5, but stick with
"import wx" for best results moving forward.

In 2.5, you will find all demo modules have changed to use the wx namespace,
as well as all contributed libs and as many samples and other stuff we can
convert over, so there won't be such confusion when you view them.

3

David Bolen wrote:

"Jeff Grimmett" <grimmtooth@softhome.net> writes:

Theoretically, "from wxPython import *" will work in V2.5, but stick with
"import wx" for best results moving forward.

In 2.5, you will find all demo modules have changed to use the wx namespace,
as well as all contributed libs and as many samples and other stuff we can
convert over, so there won't be such confusion when you view them.

Does the "import wx" support in 2.5 become non-lazy?

Yes. The real classes and other objects live in the wx package. The wxPython package has the renamers now, but they are also not lazy this time, but static assignments instead.

ยทยทยท

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