This is a question for Robin I guess. The current binary release of
wxPython-2.3.3.1-Py21 seems to be a debug/hybrid build. After upgrading
a load of systems to this latest version (to take advantage of the nice
menu-radio-buttons feature), we get lots of wxWindows C++ debug
warning-message dialogs where there were no apparent problems before.
The result is that I'm having to downgrade (and not use radio-buttons on
menus)! Will there be a "Release" build available any time soon? In the
past you posted both Release and Hybrid builds on the wxPython site.
Reworking the python code to elimiate these warnings ought to be
possible but it's made difficult as the wxWindows C++ warnnig give no
indication where the problem occurs in the python code.
I guess I could rebuild from source but I'm not familiar with
compilation on win32 systems. Can these warning be turned off without
recompilation?
This is a question for Robin I guess. The current binary release of
wxPython-2.3.3.1-Py21 seems to be a debug/hybrid build. After upgrading
a load of systems to this latest version (to take advantage of the nice
menu-radio-buttons feature), we get lots of wxWindows C++ debug
warning-message dialogs where there were no apparent problems before.
The result is that I'm having to downgrade (and not use radio-buttons on
menus)! Will there be a "Release" build available any time soon? In the
past you posted both Release and Hybrid builds on the wxPython site.
I'm only planning on doing one build per Python from now on. My reasons for this are that in almost all cases the assert messages are because you are doing something wrong and with the "release" builds there is no way to catch those besides crashing. The number one complaint about wxPython has been that it crashes a lot, so this helps take care of that and hopefully will help improve the newbies first experience with wxPython.
Also, I changed the meaning of the hybrid build with this release so that it is exactly the same as the release build except for the asserts. The various optimization flags are turned on, debug info is excluded, memory tracing is disabled, etc. So there is no additional runtime overhead compared to the old release build except for the checking the asserts.
Finally, the nextr release will have the ability (turned on by default) to turn those asserts into Python exceptions. You will also be able to set a flg to get the assert dialogs back or to ignore them entirely. This is in CVS right now if you want to build it yourself.
Reworking the python code to elimiate these warnings ought to be
possible but it's made difficult as the wxWindows C++ warnnig give no
indication where the problem occurs in the python code.
I guess I could rebuild from source but I'm not familiar with
compilation on win32 systems. Can these warning be turned off without
recompilation?
Not in the current release.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Also, I changed the meaning of the hybrid build with this release so
that it is exactly the same as the release build except for the asserts.
The various optimization flags are turned on, debug info is excluded,
memory tracing is disabled, etc. So there is no additional runtime
overhead compared to the old release build except for the checking the
asserts.
So the current binaries are a Hybrid-build (as opposed to Debug)?
Finally, the nextr release will have the ability (turned on by default)
to turn those asserts into Python exceptions. You will also be able to
set a flg to get the assert dialogs back or to ignore them entirely.
This is in CVS right now if you want to build it yourself.
Excellent! We'll hang on for the next release then.
Also, I changed the meaning of the hybrid build with this release so that it is exactly the same as the release build except for the asserts. The various optimization flags are turned on, debug info is excluded, memory tracing is disabled, etc. So there is no additional runtime overhead compared to the old release build except for the checking the asserts.
So the current binaries are a Hybrid-build (as opposed to Debug)?
Correct.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I'm trying to trace some C++ assert/debug error messages. I've
downloaded and installed the current CVS version of wxPython, with the
intention of setting the new feature to convert C++ asserts to python
exceptions. However, when I try it, it doesn't work (i.e. same behaviour
as before with C++ error boxes and no python exceptions).
Do I need a different CVS branch to get python-exceptions from C++
asserts?
Yes, WX_2_4_BRANCH.
What flags do I need to set and where do I set them.
The new behaviour is the default. There is a new method on wxApp that lets you change it back, or to ignore the asserts. You can see the details of this in the CHANGES.txt file.
Do I need
a new CVS version of wxGTK installed
You might.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!