bpo-31904: Add encoding support for VxWorks RTOS - #12051
Conversation
The main reason are: 1. The locale is frequently misconfigured. 2. Missing some functions to deal with locale in VxWorks C library.
|
@vstinner |
|
Oh sorry, the conflict is my fault. Thanks for updating the doc. Please keep the same PR. Try to fix the conflict. Use for example "git merge master". |
|
I'm the middle of a large refactoring work to enhance Python initialization: |
|
All right! We will use the same PR to fix the conflict soon. |
|
I merged your PR, thanks. It might be interesting to investigate why you have issues with locales on VxWorks, but I know that embedded devices don't really care of locales. Android had similar issues for years. But I'm fine with using UTF-8 on VxWorks. |
|
Thanks for the comments associated with locale. Locale support is in our next plan. We will investigate this. |

This is the 2nd PR successively after #11968. This PR enables encoding support for VxWorks RTOS. 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