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, loewis, mhammond
Date 2009-01-13.23:38:59
SpamBayes Score 0.0077134464
Marked as misclassified No
Message-id <>
It is not an issue with debug builds only.  The crt error handler is 
currently also reset globally for all builds which is very evil.

The current way we do thing is also not thread safe WRT other 
application threads.  On second thought though it is better to at least 
keep this modification within the bounds of the GIL.  I'll change the 
patch for that.

IMHO, the issue for the posix fd functions isn't that great, since 
hardly anyone would want to use them on windows.  The main issue is 
still the open() call.  This one is possible to avoid too without 
invoking changin the crt behaviour, by simply ramping up the 
_sanitize_mode function.

I'll put in some more effort then, because I think it is really 
important for Python to leave the crt settings alone, and still be sure 
that random input can't have unforeseen consequences.
Date User Action Args
2009-01-13 23:39:01kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, mhammond, amaury.forgeotdarc
2009-01-13 23:39:00kristjan.jonssonsetmessageid: <>
2009-01-13 23:39:00kristjan.jonssonlinkissue4804 messages
2009-01-13 23:38:59kristjan.jonssoncreate