Repository navigation
Python should support VxWorks RTOS #76085
Copy link
Copy link
Closed
Labels
3.10 (EOL)end of lifeend of lifeOS-unsupportedbuildThe build process and cross-buildThe build process and cross-buildtype-featureA feature request or enhancementA feature request or enhancement
Description
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2017-10-30.19:56:33.760>
labels = ['type-feature', '3.10', 'build']
title = 'Python should support VxWorks RTOS'
updated_at = <Date 2021-05-08.11:20:17.167>
user = 'https://github.com/kuhlenough'bugs.python.org fields:
activity = <Date 2021-05-08.11:20:17.167>
actor = 'Alex.Willmer'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2017-10-30.19:56:33.760>
creator = 'Brian Kuhl'
dependencies = []
files = []
hgrepos = []
issue_num = 31904
keywords = ['patch']
message_count = 46.0
messages = ['305249', '305511', '305657', '305690', '305869', '305877', '315365', '336680', '336742', '337083', '337867', '337909', '338964', '339059', '339898', '340244', '340245', '340310', '340385', '340406', '340409', '343004', '343008', '366073', '374361', '374460', '374469', '382014', '382020', '382021', '382023', '382198', '382218', '382276', '382525', '382793', '382807', '383009', '383096', '383097', '383098', '383226', '383259', '383467', '385461', '393247']
nosy_count = 11.0
nosy_names = ['gregory.p.smith', 'vstinner', 'christian.heimes', 'r.david.murray', 'asvetlov', 'lukasz.langa', 'Jim.Jewett', 'izbyshev', 'Brian Kuhl', 'miss-islington', 'pxinwr']
pr_nums = ['4179', '4184', '11951', '11968', '12051', '12118', '12157', '12304', '12305', '12319', '12321', '12428', '12646', '12648', '12670', '12719', '12833', '13486', '13535', '19447', '19448', '20254', '20256', '21675', '21821', '23391', '23394', '23419', '23473', '21687', '23489', '23507', '23518', '23530', '23716', '23718', '23741', '23776', '23815', '23886', '23920', '24191', '25965', '25983']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31904'
versions = ['Python 3.10']Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
3.10 (EOL)end of lifeend of lifeOS-unsupportedbuildThe build process and cross-buildThe build process and cross-buildtype-featureA feature request or enhancementA feature request or enhancement
Projects
- StatusShow more project fieldsDone
Activity
kuhlenough commentedon Oct 30, 2017
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.
terryjreedy commentedon Nov 3, 2017
The following might be relevant to this issue:
https://www.python.org/dev/peps/pep-0011/#supporting-platforms
vstinner commentedon Nov 6, 2017
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.
vstinner commentedon Nov 6, 2017
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
kuhlenough commentedon Nov 8, 2017
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.
bitdancer commentedon Nov 8, 2017
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.
ned-deily commentedon Apr 16, 2018
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.
vstinner commentedon Feb 26, 2019
Kuhl, Brian started a new discussion: [Python-Dev] VxWorks and cpython?
https://mail.python.org/pipermail/python-dev/2019-January/156024.html
PR 11968 and PR 12051 are small and reasonable.
IMHO we can take decisions on a case by case basic. But WindRiver plans to provide a buildbot and is already showing their will to propose PRs, so it seems like things are moving on.
vstinner commentedon Feb 27, 2019
New changeset 32f5fdd by Victor Stinner (pxinwr) in branch 'master':
bpo-31904: Add cross-build support for VxWorks RTOS (GH-11968)
32f5fdd
vstinner commentedon Mar 4, 2019
New changeset f4b0a1c by Victor Stinner (pxinwr) in branch 'master':
bpo-31904: Add encoding support for VxWorks RTOS (GH-12051)
f4b0a1c
32 remaining items
vstinner commentedon Dec 15, 2020
New changeset e1e3c2d by pxinwr in branch 'master':
bpo-31904: Disable os.popen and popen test cases on VxWorks (GH-21687)
e1e3c2d
vstinner commentedon Dec 15, 2020
New changeset 9a0dea6 by pxinwr in branch 'master':
bpo-31904: Skip some tests of changing owner in _test_all_chown_common() on VxWorks (GH-23716)
9a0dea6
vstinner commentedon Dec 15, 2020
New changeset b230409 by pxinwr in branch 'master':
bpo-31904: Skip os.path.expanduser() tests on VxWorks (GH-23776)
b230409
asvetlov commentedon Dec 17, 2020
New changeset ba760f3 by pxinwr in branch 'master':
bpo-31904: Skip some asyncio tests on VxWorks (bpo-23815)
ba760f3
vstinner commentedon Dec 17, 2020
New changeset 75dabfe by pxinwr in branch 'master':
bpo-31904: posixpath.expanduser() handles None user home on VxWorks (GH-23530)
75dabfe
vstinner commentedon Dec 20, 2020
New changeset ab74c01 by pxinwr in branch 'master':
bpo-31904: Fix site and sysconfig modules for VxWorks RTOS (GH-21821)
ab74c01
vstinner commentedon Jan 22, 2021
New changeset 5e45f1c by pxinwr in branch 'master':
bpo-31904: setup.py: fix cross-compilation on VxWorks (GH-24191)
5e45f1c
miss-islington commentedon May 8, 2021
New changeset 6e7fe19 by Miss Islington (bot) in branch '3.10':
[3.10] bpo-31904: Correct error string in test_file_not_exists() for VxWorks (GH-25965) (GH-25983)
6e7fe19
encukou commentedon Mar 28, 2024
All linked PRs are now closed. I plan to close the issue in a week if there are no objections.
I would advise anyone interested in supporting VxWorks to add themselves to the experts list.
vstinner commentedon Mar 28, 2024
Let's close the issue. I helped to get some VxWorks changes merged, but the issue is now idle since 2021.