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 asvetlov
Recipients Ben.Darnell, Big Stone, asvetlov, lukasz.langa, vstinner, yselivanov
Date 2019-06-23.10:31:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561285917.22.0.773927930294.issue37373@roundup.psfhosted.org>
In-reply-to
Content
I doubt if we should split a proactor loop into two objects in two threads.
I see no strong objections but have a feeling that we'll get other problems in this way. asyncio is just not designed for this mode.

The proposal looks like a very dirty hack and smells as it is.
There is no very strong reason to apply it. 
Jupiter Notebook can fix the problem on its own side in two-three lines of clear code.
History
Date User Action Args
2019-06-23 10:31:57asvetlovsetrecipients: + asvetlov, vstinner, lukasz.langa, Ben.Darnell, yselivanov, Big Stone
2019-06-23 10:31:57asvetlovsetmessageid: <1561285917.22.0.773927930294.issue37373@roundup.psfhosted.org>
2019-06-23 10:31:57asvetlovlinkissue37373 messages
2019-06-23 10:31:57asvetlovcreate