Hi all,
Most of you probably know that most of the times that that there was need for a Python specific version of some class or function in addition to the wrapped C++ one that they are named wx.PySomething. That naming pattern was also used for most things that were only in wxPython and not in C++. This all started back before there was a "wx" package name, and so they were all really wxPySomething and the "wxPy" meant that it is for "wxPython".
That was a good standard, and most of the time it was still good even after the Great Renaming that came with switching to the wx package. But there was one that has bugged me since then, and that is wx.PyAssertionError. Because if you look at it without the prefix it is just "PyAssertionError" and from the name that would make me think that it is a Python error. But it isn't. It's an exception raised in response to a wxWidgets assertion, so I've been thinking of changing the name in Phoenix to be WxAssertionError. I can also add an alias named PyAssertionError to help the transition, but I don't think I can get it to raise a deprecation warning because of how exception classes work.
Thoughts? Opinions?
···
--
Robin Dunn
Software Craftsman
http://wxPython.org