classification
Title: Python should support VxWorks RTOS
Type: enhancement Stage: patch review
Components: Cross-Build Versions: Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Alex.Willmer, Brian Kuhl, lukasz.langa, ned.deily, r.david.murray, terry.reedy, vstinner
Priority: normal Keywords: patch

Created on 2017-10-30 19:56 by Brian Kuhl, last changed 2018-04-16 19:40 by ned.deily.

Pull Requests
URL Status Linked Edit
PR 4179 closed Brian Kuhl, 2017-10-30 20:46
PR 4184 open Brian Kuhl, 2017-10-31 03:13
Messages (7)
msg305249 - (view) Author: Brian Kuhl (Brian Kuhl) * Date: 2017-10-30 19:56
With the trend to use REST APIs between the cloud and the IoT there is increasing interest in Python on embedded devices.  Cloud developer’s typical release a reference REST implementation of JSON and/or Python on Linux and leave it to the device developer to adapt it to their platform.   While many devices use eLinux, others with IP and/or hard real-time constraints need a commercial RTOS platform. 

Currently the automake configure explicitly prevents configuration of VxWorks as a build target.

I'll provide a pull request referencing this issue with the required changes.
msg305511 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2017-11-03 21:01
The following might be relevant to this issue:
https://www.python.org/dev/peps/pep-0011/#supporting-platforms
msg305657 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2017-11-06 16:55
To support a new platform, you need a developer who can support this platform next years, a working buildbot, etc. You can start a discussion on python-dev to get a first feedback.

Without a strong support, this issue should be fixed a REJECTED and a patch should be maintainted out of the tree. Since the PR seems small, it should be "easy" to keep a fork of CPython up to date.
msg305690 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2017-11-06 23:39
FYI I already started a thread on python-dev:
[Python-Dev] Partial support of a platform
https://mail.python.org/pipermail/python-dev/2017-November/150238.html
msg305869 - (view) Author: Brian Kuhl (Brian Kuhl) * Date: 2017-11-08 16:00
I'm quite happy to take on maintainer role for Python on VxWorks, so I think we can get that one solved. 

Enabling a build bot for cross compile of propitiatory OS presents a number of legal licensing issues that outside my control. And I'll discuss it internally at Wind River. However I think it is in line with where our customers want us to go, so well worth pursuing. 

I'll keep this pull request active and up to date, till the broader issues you have raised can be resolved.      

I'll post a proposal on the mailing list after I consulted within Wind River.

Many thanks for your interest and support.
msg305877 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2017-11-08 16:23
I'm not sure what licensing issues you are talking about, but setting up a buildbot shouldn't normally run into any.  As long as you have a license to the run the OS, the fact that you are using it to receive jobs from our build master and run them shouldn't be a problem.  You can keep the whole thing behind a firewall in a DMZ: the slave makes outbound connections to pick up its jobs.

On the other hand, the logistics of setting up a cross compile buildbot might be a bit complex, I've never done that.  You might need specific support from our build master.  In any case, the python-buldbots mailing list is the place to talk if you want to/can pursue this.
msg315365 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2018-04-16 19:40
As I commented on the PR, I think this PR should not be merged until and if there is a consensus that this support belongs in the standard cpython repo and there is an agreed-upon plan how this platform would be supported on going.  I think it needs an approved PEP.  We've allowed ourselves in the past to do a long-term disservice to our downstream users by merging in support for platforms that we were not equipped to support.  In any case, it would need to wait for 3.8.
History
Date User Action Args
2018-04-16 19:40:29ned.deilysetnosy: + lukasz.langa, ned.deily

messages: + msg315365
versions: + Python 3.8, - Python 3.7
2017-11-08 16:23:25r.david.murraysetnosy: + r.david.murray
messages: + msg305877
2017-11-08 16:00:46Brian Kuhlsetmessages: + msg305869
2017-11-06 23:39:05vstinnersetmessages: + msg305690
2017-11-06 16:55:23vstinnersetnosy: + vstinner
messages: + msg305657
2017-11-03 21:01:04terry.reedysetnosy: + terry.reedy
messages: + msg305511
2017-10-31 03:13:38Brian Kuhlsetpull_requests: + pull_request4155
2017-10-30 20:46:47Brian Kuhlsetkeywords: + patch
stage: patch review
pull_requests: + pull_request4149
2017-10-30 19:56:33Brian Kuhlcreate