C.A.M. Gerlach <cam.gerl...@gerlach.cam> added the comment:

Sorry I never got around to this, I was planning on it and then life and COVID 
intervened. I can give it another look now to get it in before the 3.10 feature 
freeze (since I at least documented in detail what each change should be, so it 
should be relatively straightforward) unless someone else would rather take it.

> PEP 11 says that "[a] new feature release X.Y.0 will support all Windows 
> releases whose extended support phase is not yet expired". There was no such 
> thing as Extended Security Updates (ESU) when that provision was accepted. As 
> defined by PEP 11, extended support for Windows 7 ended on 2020-01-14. 

Yeah, "Extended Support" has a very specific, defined meaning [1] in Microsoft 
standard terminology (and other vendors as well), as the support phase after 
"Mainstream Support" but before the product end of life, where security updates 
and potentially limited bugfixes are still offered to all customers and the 
product is still considered supported, but new features and phone support is 
not. This ended 2020-01-24.

[1] https://docs.microsoft.com/en-us/lifecycle/policies/fixed

ESU [2] is a specialized, paid program available to high volume enterprise 
customers as a "last resort option" that pay big $$$ to continue receiving 
critical security updates for a limited time. This fulfills neither the letter 
nor the spirit of the policy defined in PEP 11; if such vendors need support 
for bleeding-edge Python versions for some reason, it certainly should be well 
within their means to fund someone to do so.

[2] https://docs.microsoft.com/en-us/lifecycle/faq/extended-security-updates

----------
versions: +Python 3.10 -Python 3.9

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32592>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to