renamed wx.PyAssertionError

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxPython/Phoenix/trunk@69923 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/MigrationGuide.txt

@@ -176,8 +176,8 @@ that is using the old names to use the new ones instead::
 
 
 
-wx.PyDeadObjectError
----------------------
+wx.PyDeadObjectError --> RuntimeError
+-------------------------------------
 
 Classic wxPython tracks when the C++ part of some types of objects (pretty
 much just window types) is destroyed and then replaces the proxy object's
@@ -191,4 +191,15 @@ conditional statement to see if it is safe to use, like this::
     if someWindow:
         doSomething()
         
-        
+        
+        
+wx.PyAssertionError --> wx.wxAssertionError
+-------------------------------------------
+
+This is the exception raised when one of the wxASSERT (or similar) statements
+in the wx C++ code fails. Since it is a wxWidgets assertion and not a
+wxPython assertion the name was changed to make that a little more clear. A
+compatibility alias exists so using wx.PyAssertionError will still work, but
+you should migrate those uses to wx.wxAssertionError if possible.
+
+