[Python-Dev] Compiling without multithreading support -- still useful?
Christian Heimes
christian at python.org
Tue Sep 5 13:08:21 EDT 2017
More information about the Python-Dev mailing list
Tue Sep 5 13:08:21 EDT 2017
- Previous message (by thread): [Python-Dev] Compiling without multithreading support -- still useful?
- Next message (by thread): [Python-Dev] Compiling without multithreading support -- still useful?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2017-09-05 09:42, Victor Stinner wrote: > I proposed to drop the --without-threads option multiple times. I > worked on tiny and cheap embedded devices and we used Python *with* > threads for concurrency. Many Python features require threads, like > asyncio and multiprocessing. Also subprocess.communicate() on Windows, > no? > > I'm strongly in favor of dropping this option from Python 3.7. It > would remove a lot of code! +1 These days, tiny embedded devices can make use of MicroPython. Christian
- Previous message (by thread): [Python-Dev] Compiling without multithreading support -- still useful?
- Next message (by thread): [Python-Dev] Compiling without multithreading support -- still useful?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list