What exactly does the PR involve? Is it a relatively simple compatibility patch or something that adds significant amounts of platform-specific code? The former can be reviewed (and potentially merged) by any core dev knowledgeable in the areas being changed, but the latter requires long-term support for the platform.
In order to provide support for a new platform that we don't presently have support for in CPython, it requires the following: 1) An existing core developer willing to provide long-term support for the platform. Alternatively, someone else can be granted commit privileges, for the purpose of maintaining that platform and fixing any issues that come up in that CI that are specific to it. However, this is done on a case-by-case basis, as it still requires a decent amount of trust with that individual. 2) A stable buildbot provided, to test against new changes made to CPython. The purpose of the above is to ensure that any substantial platform-specific code added to CPython receives proper care; this is opposed to a large addition of new code for a platform that has nobody to take care of it when issues come up. Especially as a group of mostly volunteers (and those paid by their employers to contribute), the latter wouldn't be sustainable. I personally think it would be fantastic to have official support for real-time OSs in CPython, but in this ecosystem, it requires being able to place trust in someone that's willing and adequately proficient in the related areas to provide long-term support for them. For more details, see PEP 11: https://www.python.org/dev/peps/pep-0011/#supporting-platforms. On Wed, Aug 5, 2020 at 7:44 AM Xin, Peixing <peixing....@windriver.com> wrote: > Hi, Python developers: > > > > Anyone interested in PR review and merging for VxWorks RTOS? We can give a > proper pay for that. Contact me if you have interest. > > > > Thanks, > > Peixing > > > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/HATTYX3BWEIPVVUL7FMSNSCFYOBPS6OD/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/ZT2RA7KT7AFMAXTKDQGQOQ6TCUXWE5QT/ Code of Conduct: http://python.org/psf/codeofconduct/
