[wxPython-users] Just upgraded to wx 2.8

[Rooney, Mike (ext. 324)]

>I would image that backwards compatability would be a very high priority f=
or whomever the powers-that-be who decide to update wxPython, right?  If I =
go through this exercise, what's to say that I won't have to go through it =
again in 2 years when backwards compatability is again not maintained ?
 =

I am not sure how much you have followed this but it really has very little=
 to do with wx. It was basically a python-wide decision to stop importing *=
, and wx just followed along. Even a few years ago (in fact, probably alway=
s), people were warning of the dangers of importing * and saying never to d=
o it, except in wx! So technically, wx has been maintaining backwards compa=
tibility for a long time and as someone else mentioned this method of impor=
ting has been deprecated for quite a while.
 =

The point is, wx didn't just decide to do something different for the heck =
of it. The arguments against importing * just became too strong and the adv=
antages of using namespaces became too apparent. This is a change you shoul=
d be making if possible no matter what module/package you are using.
 =

I hope this has helped to clear things up. If I have incorrectly stated any=
thing hopefully someone else will chime in. Perhaps wx's generousity in let=
ting you avoid namespaces for so long has caused you more pain in the end :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wxwidgets.org/pipermail/wxpython-users/attachments/200702=
01/07ba809b/attachment.htm