This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mhammond
Recipients amaury.forgeotdarc, kristjan.jonsson, loewis, mhammond
Date 2009-01-02.22:21:27
SpamBayes Score 2.4784087e-05
Marked as misclassified No
Message-id <>
Can anyone point me at a test that failed in this case?  A quick look
over winsig.c shows no asserts.  I didn't compare the vs2005 crt source
though, so its highly likely I just missed it...

On the broader point, it could be argued that if it is the apps
responsibility to re-enable assertions, it is also the apps
responsibility to disable them in the first place.  If other libraries
on the system attempted the same as Python, it would obviously be
undefined if Python's attempt had any actual affect - the last called
would win.  As we found with the old locale() issues, we really can't
rely on Python setting a global shared state to keep things nice.  From
a pragmatic POV, if we know the MS crt asserts on certain constants
signal numbers, can't we just avoid passing those numbers?
Date User Action Args
2009-01-02 22:21:28mhammondsetrecipients: + mhammond, loewis, amaury.forgeotdarc, kristjan.jonsson
2009-01-02 22:21:28mhammondsetmessageid: <>
2009-01-02 22:21:28mhammondlinkissue4804 messages
2009-01-02 22:21:27mhammondcreate