(original) (raw)

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@pitrou.net> wrote:

On Wed, 6 Sep 2017 10:50:11 -0700
Ethan Smith <ethan@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/thread\_nothreads.h where
PyThread\_start\_new\_thread() 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@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/ethan%40ethanhs.me