[issue5116] expose _CrtSetReportMode via the msvcrt module

Changes by Terry J. Reedy : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue5116] expose _CrtSetReportMode via the msvcrt module

Changes by Brian Curtin : -- keywords: +26backport -needs review, patch, patch stage: -> needs patch versions: -Python 3.0, Python 3.1 ___ Python tracker ___ ___

[issue5116] expose _CrtSetReportMode via the msvcrt module

Brian Curtin added the comment: I just noticed that this already exists in py3k, added in r57823 (lacks docs but I'll cover them in the py3k fix for #7579) -- ___ Python tracker

[issue5116] expose _CrtSetReportMode via the msvcrt module

Amaury Forgeot d'Arc added the comment: _CrtSetReportMode() is exposed without the leading underscore. IMO the _CRT_WARN and other constants should be renamed the same way. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue5116] expose _CrtSetReportMode via the msvcrt module

Brian Curtin added the comment: Has there been any consensus about what to do with this? I know there was some chatter on python-dev about assertions causing problems with buildbots (6 months ago?) but I don't think anything came out of it. The code change is small and looks good. Is it worth e

[issue5116] expose _CrtSetReportMode via the msvcrt module

Changes by Mark Hammond : -- components: +Windows ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue5116] expose _CrtSetReportMode via the msvcrt module

New submission from Mark Hammond : In bug 4804, there is some debate about how desirable it is for Python to unconditionally disable all CRT assertions on Windows - however, there is agreement that exposing the ability to enable and disable these assertions via the msvcrt module is reasonable - s