[Python-Dev] Compiling without multithreading support -- still useful? (original) (raw)

Ethan Smith ethan at ethanhs.me
Wed Sep 6 14:23:29 EDT 2017

Certainly, I understand it can be burdensome. I suppose I can use 3.6 branch for the initial port, so it shouldn't be an issue.

On Wed, Sep 6, 2017 at 11:13 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:

On Wed, 6 Sep 2017 10:50:11 -0700 Ethan Smith <ethan at ethanhs.me> wrote: > I think this is useful as it can make porting easier. I am using it in my > attempts to cross compile CPython to WebAssembly (since WebAssembly in its > MVP does not support threading).

The problem is that the burden of maintenance falls on us (core CPython developers), while none of us and probably 99.99% of our userbase have absolutely no use for the "functionality". Perhaps there's a simpler, cruder way to "support" threads-less platforms. For example a Python/threadnothreads.h where PyThreadstartnewthread() would always fail (and with trivial implementations of locks and TLS keys). But I'm not sure how much it would help those porting attempts. Regards Antoine.

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ ethan%40ethanhs.me -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170906/32e03c10/attachment.html>

More information about the Python-Dev mailing list