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.

Author stefan
Recipients asvetlov, stefan, vstinner, yselivanov
Date 2019-01-08.00:48:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1546908512.18.0.786568541744.issue35635@roundup.psfhosted.org>
In-reply-to
Content
OK, so while I have been able to work around the issues (by using `quamash` to bridge between `asyncio` and `Qt`), I'd still like to understand the rationale behind the limitation that any subprocess-managing event-loop has to run in the main thread. Is this really an architectural limitation or a limit of the current implementation ?

And to your question: As I wasn't really expecting such a limitation, I would have expected 
    "To handle signals and to execute subprocesses, the event loop must be run in the main thread."

to be written much more prominently (as a warning admonition even, perhaps).
History
Date User Action Args
2019-01-08 00:48:34stefansetrecipients: + stefan, vstinner, asvetlov, yselivanov
2019-01-08 00:48:32stefansetmessageid: <1546908512.18.0.786568541744.issue35635@roundup.psfhosted.org>
2019-01-08 00:48:32stefanlinkissue35635 messages
2019-01-08 00:48:32stefancreate