3 ms·
> I have to contrast this attitude to CPython, who, while I'm sure they never originally said that their code was designed to run on s390 (risc-v, pick your arc
by 323 4y ago
> I have to contrast this attitude to CPython, who, while I'm sure they never originally said that their code was designed to run on s390 (risc-v, pick your architecture..), would not go ahead with a change that froze out these users.
You have a wrong recollection of history. CPython removed support for several platforms, including former major ones like Windows XP and Vista.
> Attached PR removes code to support Windows Vista.
https://bugs.python.org/issue32592 https://bugs.python.org/issue32592
And Python 3.9+ doesn't work anymore on Windows 7:
https://discuss.python.org/t/windows-7-support-for-python-3-9-or-3-10-without-a-fork/13842 https://discuss.python.org/t/windows-7-support-for-python-3-...
- tyingq 4y agoPerl might be a better stand in for the argument. It has supported oddball platforms for its entire history, with pretty extensive build support that checks for lots of platform specific settings.
- whartung 4y ago“Congratulations! You aren’t running Eunice!” From the early Perl configuration script.
- ris 4y agoI'm not counting platforms removed because of deprecation.
- spenczar5 4y agoSurely Hewlett Packard’s 1990s CPUs are at least as deprecated as Windows 7? Or IBM’s System 390 mainframes, which were discontinued in 2004? What is the difference?