Stefan Krah added the comment:
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
Changes by Guido van Rossum gu...@python.org:
--
assignee: - gvanrossum
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19295
___
New submission from Stefan Krah:
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.
--
keywords: buildbot
messages: 200399
nosy: gvanrossum, skrah
priority: low
severity: normal
stage: needs patch
Stefan Krah added the comment:
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.
--
keywords: +patch
Added file: http://bugs.python.org/file3/issue19295.patch
Roundup Robot added the comment:
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
--
nosy: +python-dev
___
Python tracker
Guido van Rossum added the comment:
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
