This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Make asyncio work without threads
Type: behavior Stage: needs patch
Components: Versions: Python 3.4
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: gvanrossum Nosy List: gvanrossum, python-dev, skrah
Priority: low Keywords: buildbot, patch

Created on 2013-10-19 10:31 by skrah, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
issue19295.patch skrah, 2013-10-19 10:37 review
Messages (5)
msg200399 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2013-10-19 10:31
I'm referring to msg200288.  I guess this is low priority, since
not many people will want to use asyncio on a build --without-threads.
msg200400 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2013-10-19 10:37
Meanwhile, the patch addresses the buildbot failure.  I currently don't
have access to the machine with my ssh-key, so I can't commit the patch
right now.
msg200428 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2013-10-19 15:49
New changeset 1c281f3de48f by Guido van Rossum in branch 'default':
Skip the asyncio tests when threads are not available.
http://hg.python.org/cpython/rev/1c281f3de48f
msg200528 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2013-10-20 00:34
I looked into this a bit more and it's tricky, because without threads, asyncio/futures.py can't import some base exceptions concurrent.futures. Also, some tests create servers in separate threads, and getaddrinfo() would of course block.

Not sure if I'll ever want to support this...
msg200562 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2013-10-20 10:43
> Not sure if I'll ever want to support this...

I think it can be closed as "wont-fix". We had a poll on python-dev
about --without-threads a while ago, and the only systems that needed
it were older OpenBSD systems and a Fujitsu supercomputer with the
Fujitsu compiler.
History
Date User Action Args
2022-04-11 14:57:52adminsetgithub: 63494
2013-10-20 16:44:52gvanrossumsetstatus: open -> closed
assignee: gvanrossum
resolution: wont fix
2013-10-20 10:43:26skrahsetmessages: + msg200562
2013-10-20 00:34:16gvanrossumsetmessages: + msg200528
2013-10-19 15:49:41python-devsetnosy: + python-dev
messages: + msg200428
2013-10-19 10:37:08skrahsetfiles: + issue19295.patch
keywords: + patch
messages: + msg200400
2013-10-19 10:31:06skrahcreate