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 kristjan.jonsson
Recipients amaury.forgeotdarc, kristjan.jonsson, mhammond
Date 2009-01-02.09:56:18
SpamBayes Score 0.04449446
Marked as misclassified No
Message-id <>
In-reply-to <>
It occurred to me that a more gentle way to do this is to disable the functionality only around close().
This is far less intrusive, for example, in an embedded environment.
I must confess that I had completely forgototten about the disabling of the assertion and only stumbled on this recently when I was trying to find out why none of my _ASSERTS in eve worked!  Making wholesale CRT settings certainly should be avoided.

So, as I said, we could very well avoid this by just wrapping a few instances of close() with a CrtSetErrorHandler calls and friends.  With the caveat that these are not threadsafe, that is, it is a process global setting for the CRT.  But toggling it during a limited scope surely is less intrusive than modifying it for the entire process permanently.

Date User Action Args
2009-01-02 09:56:19kristjan.jonssonsetrecipients: + kristjan.jonsson, mhammond, amaury.forgeotdarc
2009-01-02 09:56:19kristjan.jonssonlinkissue4804 messages
2009-01-02 09:56:18kristjan.jonssoncreate