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 steve.dower
Recipients steve.dower, tim.golden, vstinner, zach.ware
Date 2015-02-12.14:17:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423750639.26.0.597512478999.issue23314@psf.upfronthosting.co.za>
In-reply-to
Content
_Py_verifyfd has to go away, unfortunately. It requires inside knowledge of the exact CRT version, and with VC14 the CRT will automatically upgrade so that we're always using the latest.

I've gotten a function added to the CRT to make it unnecessary for release builds (which terminate on invalid fds). However, debug builds will display a message box still, which affects the buildbots. test already suppresses the dialogs for its own process, but when it creates subprocesses they don't inherit that setting.

An environment variable is an easy way to make sure that all subprocesses also have assert dialogs disabled. In release builds they are always disabled, hence the _DEBUG check.
History
Date User Action Args
2015-02-12 14:17:19steve.dowersetrecipients: + steve.dower, vstinner, tim.golden, zach.ware
2015-02-12 14:17:19steve.dowersetmessageid: <1423750639.26.0.597512478999.issue23314@psf.upfronthosting.co.za>
2015-02-12 14:17:19steve.dowerlinkissue23314 messages
2015-02-12 14:17:19steve.dowercreate