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 Carsten Fuchs, CharlieClark, Dominik Geldmacher, Manjusaka, eryksun, jeremy.kloth, jkloth, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2020-02-12.09:43:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Will Python support a release for as long as it's supported by the enterprise version? For example, support for 1709 enterprise ends on 2020-04-14, so if we followed that, then Python 3.9 would require Windows 10 1803 or higher. That seems wrong while we're still supporting Windows 8.1, but what will the stance be when Python supports only Windows versions that use the modern lifecycle?

This needs a separate discussion on python-dev, but for issues like this I think it's fine to blame the underlying platform and recommend getting their updates. We don't have to work around every Windows bug for all time.

I'll read the rest of what's been happening on this issue when I'm less tired, but not quite up to it right now ;)
Date User Action Args
2020-02-12 09:43:03steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, tim.golden, jkloth, jeremy.kloth, zach.ware, eryksun, Manjusaka, CharlieClark, Dominik Geldmacher, Carsten Fuchs
2020-02-12 09:43:03steve.dowersetmessageid: <>
2020-02-12 09:43:03steve.dowerlinkissue36792 messages
2020-02-12 09:43:03steve.dowercreate