bpo-31904: Add posix module support for VxWorks RTOS#12118
Conversation
|
@pablogsal @izbyshev @nanjekyejoannah: Would you min to review this change? |
Sorry, something went wrong.
izbyshev
left a comment
There was a problem hiding this comment.
Is there any plan to update documentation to reflect that some functions that are normally available on Unix are not actually available on VxWorks? With this patch, they are os.fork, os.exec* and os.spawn*p*.
Sorry, something went wrong.
Have updated os.rst about this. |
Sorry, something went wrong.
|
@izbyshev @pablogsal I've fixed all the issues reviewed out. Could you help to review again when available? Thanks a lot. |
Sorry, something went wrong.
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
Your change seems reasonable, but I have a few comments.
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
Your PR mostly LGTM, but I have a few more comments before being able to approve it.
Sorry, something went wrong.
|
LGTM except if the typo. Please fix the typo, so I can merge your PR ;-) |
Sorry, something went wrong.
|
Thanks @pxinwr! I know that this one was painful, but well, the os ("posix") module is where you can find most differences between operating systems. |
Sorry, something went wrong.
This is the successive PR after #11968. This PR enables posix module support for VxWorks RTOS. VxWorks doesn't support fork()/exec(). Instead, we use rtpSpawn() to spawn new processes.
More and full support on modules for VxWorks will continuously be added by the coming PRs.
VxWorks is a product developed and owned by Wind River. For VxWorks introduction or more details, go to https://www.windriver.com/products/vxworks/
Wind River will have a dedicated engineering team to contribute to the support as maintainers.
We already have a working buildbot worker internally, but has not bound to master. We will check the process for the buildbot, then add it.
https://bugs.python.org/issue31904