> The PEP 11 has a nice description to get a *full* support of a new platform: > https://www.python.org/dev/peps/pep-0011/ PEP 11 defines the endpoint, full support, and several requirements to call a platform fully supported. It would be nice if a process was defined for getting from "no support" to "full support." I think that to be as supportive as possible (no pun intended), it would make sense to grant people check-in privileges to a branch (if that's possible or desirable), or, if not, list forks which are intended to add support for various platforms which are moving toward full support. I don't know if PEP 11 is the right place to track such activity, relatively few updates should be required. I doubt it will be an onerous burden. Something like: * ButterflyOS - Victor Stinner (victor.stinner at gmail.com) is working to add CPython support for this platform on this Git branch: https://github.com/python/Butterfly * MothOS - Skip Montanaro (skip.montanaro at gmail.com) is working to add CPython support for this platform on this Git branch: https://github.com/smontanaro/Moth Interested parties would be directed to contact the pilots of those branches if they wanted to contribute. Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4