[Python-Dev] What is the workflow for announcing tier 2 platform support?

[Victor Stinner]

Hi,

I don't think that we can say that Python supports VxWorks yet. Many PRs
are not merged yet. You are free to disrribute a modified version with your
changes.

The PEP 11 lists conditions to fully support a platform:
https://www.python.org/dev/peps/pep-0011/

My summary is: all tests must pass (it's ok to skip a few), a buildbot must
run and a core dev should handle any regression.

I expect that VxWorks will better fit in the "Best Effort" category: only
fix issues when someone proposes a fix.

See also my notes:
https://pythondev.readthedocs.io/platforms.html

Victor


Le mardi 19 mars 2019, Xin, Peixing <Peixing.Xin at windriver.com> a écrit :
> Hi, Experts:
>
>
>
> VxWorks RTOS will release a new version at the end of June. For this new
version, we(Wind River) plan to announce the Python support officially here
(https://www.python.org/download/other/) for VxWorks as tier 2 platform.
Now my 2 questions come:
>
> 1.       To be qualified as tier 2 platform here
https://www.python.org/download/other/, do I need to get all test cases
pass on VxWorks RTOS? Now we have the following PRs for VxWorks. With these
PRs merged, we can get around 70% test cases PASS.
>
> </mail/u/0/s/?view=att&th=16993e40c3ae8b1e&attid=0.0.1&disp=emb&zw&atsh=1>
>
> 2.       If we reach the announcement level, what is the workflow to
update the website statements here https://www.python.org/download/other/.
The following picture shows what we want to show.
>
>
>
> </mail/u/0/s/?view=att&th=16993e40c3ae8b1e&attid=0.0.2&disp=emb&zw&atsh=1>
>
>
>
> Thanks,
>
> Peixing
>
>

-- 
Night gathers, and now my watch begins. It shall not end until my death.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190319/d0e48a72/attachment.html>