wxWidgets/wxPython/distrib
2001-05-23 15:05:41 +00:00
..
.cvsignore merged 2.2 branch 2000-07-15 19:51:35 +00:00
.rpmrc merged 2.2 branch 2000-07-15 19:51:35 +00:00
autobuild.py Updated distribution stuff 2000-12-11 04:00:06 +00:00
make_installer.py some minor changes for the installer flags 2001-05-23 15:05:41 +00:00
makedbg.bat Merged wxPython 2.2.2 over to the main branch 2000-10-30 21:08:42 +00:00
makedemo Switched to InnoSetup for MSW distributions 2001-04-30 18:32:18 +00:00
makedev.bat merged 2.2 branch 2000-07-15 19:51:35 +00:00
makerpm merged 2.2 branch 2000-07-15 19:51:35 +00:00
maketgz merged 2.2 branch 2000-07-15 19:51:35 +00:00
makexferzip merged 2.2 branch 2000-07-15 19:51:35 +00:00
makexferzip.bat merged 2.2 branch 2000-07-15 19:51:35 +00:00
README.dbg.txt Merged wxPython 2.2.2 over to the main branch 2000-10-30 21:08:42 +00:00
wise.aut merged 2.2 branch 2000-07-15 19:51:35 +00:00
wxPython.bmp merged 2.2 branch 2000-07-15 19:51:35 +00:00
wxPython.rsp Merged wxPython 2.2.2 over to the main branch 2000-10-30 21:08:42 +00:00
wxPython.wse Copied/merged from the 2.2 branch. 2001-02-16 08:19:50 +00:00
wxPython.WSM Copied/merged from the 2.2 branch. 2001-02-16 08:19:50 +00:00
zipall.bat Copied/merged from the 2.2 branch. 2001-02-16 08:19:50 +00:00
zipit.bat Merged wxPython 2.2.2 over to the main branch 2000-10-30 21:08:42 +00:00

This zip file contains versions of the wxWindows and wxPython binaries
that have been compiled with __WXDEBUG__ defined.  This adds code to
wxWindows that is a bit more agressive about checking parameter
values, return values, and etc.  When the debugging library senses
something is wrong it will popup a message dialog telling you so.
Unfortunately the message is specific to the C++ code but it might
give you a hint about what went wrong and how to fix it.

Another debugging feature is when the wxPython program exits, it will
print to stdout information about any wxWindows C++ objects that
havn't been properly cleaned up.

This archive contains a new wxWindows DLL named wx[version]d.dll and a
debugging version of the core wxPython module, wxc_d.pyd.  These
should be put into your wxPython package directory.  Also included are
the debuging version of Python, python_d.exe and python[VER]_d.dll
which can be put wherever you like.

In order to run the debugging version of wxPython sumply run you
program with python_d.exe instead of python.exe.  This lets the
debugging version sit side by side with the production version, with
no need for swapping this around.  You will also need _d versions of
any other extension modules you are using.  If you need _d's for any
of the other standard Python extensions you can get them here, for 2.0
at least:

http://www.pythonlabs.com/products/python2.0/downloads/BeOpen-Python-2.0-Debug.zip


Robin