On 01/04/2022 01.40, Victor Stinner wrote:
Hi,
I don't think that the current PEP 11 draft (*) describes correctly the current status of a bunch of platforms which are not "actively" supported. I like to call these plaforms as "best effort support" platforms. I propose considering adding an explicit "Tier 3" to PEP 11.
(*) https://github.com/python/peps/pull/2442/
Rust defines its Tier 3 as: "Tier 3 targets are those which the Rust codebase has support for, but which the Rust project does not build or test automatically, so they may or may not work."
Tier 3 requirements would be *very weak*:
- No buildbot requirement
- No assigned core dev needed
- Don't revert a change breaking a Tier 3 platform
- Don't hold a Python release if a Tier 3 platform is broken
As Brett pointed out a tier 3 platform does not make much sense if we have no means to test the platform. I also would like to nudge vendors to contribute resources like build bots or engineering time. We want a low bar for contributions. No bar is too low. :)
How about:
a buildbot is required. For a transition period a public CI system, that runs Python's test suite at least once per day, is also acceptable.
at least one active contributor who acts as a point of contact, monitors CI and provides fixes in a timely fashion.
Christian