]>
Commit | Line | Data |
---|---|---|
1 | This zip file contains versions of the wxWindows and wxPython binaries | |
2 | that have been compiled with __WXDEBUG__ defined. This adds code to | |
3 | wxWindows that is a bit more agressive about checking parameter | |
4 | values, return values, and etc. When the debugging library senses | |
5 | something is wrong it will popup a message dialog telling you so. | |
6 | Unfortunately the message is specific to the C++ code but it might | |
7 | give you a hint about what went wrong and how to fix it. | |
8 | ||
9 | Another debugging feature is when the wxPython program exits, it will | |
10 | print to stdout information about any wxWindows C++ objects that | |
11 | havn't been properly cleaned up. | |
12 | ||
13 | This archive contains a new wxWindows DLL named wx[version]d.dll and a | |
14 | debugging version of the core wxPython module, wxc_d.pyd. These | |
15 | should be put into your wxPython package directory. Also included are | |
16 | the debuging version of Python, python_d.exe and python[VER]_d.dll | |
17 | which can be put wherever you like. | |
18 | ||
19 | In order to run the debugging version of wxPython sumply run you | |
20 | program with python_d.exe instead of python.exe. This lets the | |
21 | debugging version sit side by side with the production version, with | |
22 | no need for swapping this around. You will also need _d versions of | |
23 | any other extension modules you are using. If you need _d's for any | |
24 | of the other standard Python extensions you can get them here, for 2.0 | |
25 | at least: | |
26 | ||
27 | http://www.pythonlabs.com/products/python2.0/downloads/BeOpen-Python-2.0-Debug.zip | |
28 | ||
29 | ||
30 | Robin |