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 mbussonn
Recipients asvetlov, brett.cannon, mbussonn, minrk, njs, pmpp, willingc, xtreak, yselivanov
Date 2019-05-01.19:48:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1556740090.28.0.265236918834.issue34616@roundup.psfhosted.org>
In-reply-to
Content
Extra notes from in-person discussion; 
We might want a both a Sync-REPL and Async-REPL `compile()` mode depending on wether the REPL support async. 

One of the other question was wether `exec` should look at wether an eventloop is running, or if it should just return a coroutine and it's the -programmer job to check wether there is an event loop or not and do the right thing. 

Also for info all the top level async-await PR and issues on IPython can be found here: https://github.com/ipython/ipython/issues?q=label%3Aasync%2Fawait+is%3Aclosed
History
Date User Action Args
2019-05-01 19:48:10mbussonnsetrecipients: + mbussonn, brett.cannon, njs, asvetlov, pmpp, yselivanov, willingc, minrk, xtreak
2019-05-01 19:48:10mbussonnsetmessageid: <1556740090.28.0.265236918834.issue34616@roundup.psfhosted.org>
2019-05-01 19:48:10mbussonnlinkissue34616 messages
2019-05-01 19:48:10mbussonncreate