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 glaubitz
Recipients Arfrever, christian.heimes, glaubitz
Date 2021-02-15.09:23:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
That's an argument I have personally never heard before and I have been dealing with a lot of architecture support in many packages.

FWIW, lots of upstream projects have targets which are officially supported and others which are there but not supported and that was never really a problem.

As long as the architectures are being maintained in the Linux kernel, GCC, binutils and glibc, they can be considered usable and maintained.

The m68k architecture for example has a very active and large community due to the popularity of retro computing. This has lead to efforts which will soon bring Rust support to M68k and the Amiga.

I therefore don't really understand what you gain when you make it harder for downstreams to use Python.
Date User Action Args
2021-02-15 09:23:28glaubitzsetrecipients: + glaubitz, christian.heimes, Arfrever
2021-02-15 09:23:28glaubitzsetmessageid: <>
2021-02-15 09:23:28glaubitzlinkissue43179 messages
2021-02-15 09:23:28glaubitzcreate