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 asvetlov, malin, methane, ned.deily, njs, paul.moore, skn78, steve.dower, thatiparthy, tim.golden, tjguk, zach.ware
Date 2018-02-07.00:00:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1517961601.96.0.467229070634.issue32394@psf.upfronthosting.co.za>
In-reply-to
Content
In this case I like the flags disappearing on older versions, just as they would if you built CPython on a version of Linux that didn't have the flags. The problem is that the Windows SDK always defines enum values for all Windows versions even if you are targeting an older version, as most APIs silently ignore unknown flags. Since there's no way to reliably remove the flags at build time, it'll have to be done at import time.

In Python, existence normally implies availability, so we should maintain that here, especially since this API raises errors with these flags.
History
Date User Action Args
2018-02-07 00:00:02steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, ned.deily, njs, asvetlov, methane, zach.ware, thatiparthy, malin, tjguk, skn78
2018-02-07 00:00:01steve.dowersetmessageid: <1517961601.96.0.467229070634.issue32394@psf.upfronthosting.co.za>
2018-02-07 00:00:01steve.dowerlinkissue32394 messages
2018-02-07 00:00:01steve.dowercreate