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 veso266
Recipients CAM-Gerlach, DMI-1407, ZackerySpytz, eryksun, izbyshev, lukasz.langa, paul.moore, pitrou, python-dev, steve.dower, terry.reedy, tim.golden, veso266, zach.ware
Date 2021-03-24.12:44:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
not sure about the strategies here but maybe a better approach would be to kill support for unsupported version of windows in a major release
since I guess python 3 was a complete rewrite of python2 (at least the low level side I assume it was) 

and it would be easier for people to remeber (eg, if I have to rewrite my app because python4 has a major language differences I might as well drop support for older OSes in it), eg, python2 works on XP, python3 works on vista and up, python4 works on windows 10

for instance, I didn't even know you can run python3 on XP, I always thought that python2.7 is the last version that would run there

and since the code to support windows 7 is still present (almost, just the installer change would need to be rolleed back and some compiler declaratives:

I see no reason to touch it (it probably just stays there serving its purpose) and when python4 comes along (if its a rewrite then windows 7 hacks (would just not be written anymore)
Date User Action Args
2021-03-24 12:44:09veso266setrecipients: + veso266, terry.reedy, paul.moore, pitrou, tim.golden, lukasz.langa, python-dev, zach.ware, eryksun, steve.dower, izbyshev, ZackerySpytz, CAM-Gerlach, DMI-1407
2021-03-24 12:44:09veso266setmessageid: <>
2021-03-24 12:44:09veso266linkissue32592 messages
2021-03-24 12:44:08veso266create