[issue24638] asyncio "loop argument must agree with future" error message could be improved

2019-05-03 Thread Andrew Svetlov
Andrew Svetlov added the comment: New changeset 4737b923df6fbdb9e2bf3fdccea2112270556e0a by Andrew Svetlov (Zackery Spytz) in branch 'master': bpo-24638: Improve the error message in asyncio.ensure_future() (#12848)

[issue24638] asyncio "loop argument must agree with future" error message could be improved

2019-05-03 Thread Andrew Svetlov
Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue24638] asyncio "loop argument must agree with future" error message could be improved

2019-04-15 Thread Zackery Spytz
Zackery Spytz added the comment: I've created a PR for this issue. -- components: +asyncio nosy: +ZackerySpytz, asvetlov, yselivanov versions: +Python 3.8 ___ Python tracker

[issue24638] asyncio "loop argument must agree with future" error message could be improved

2019-04-15 Thread Zackery Spytz
Change by Zackery Spytz : -- keywords: +patch pull_requests: +12773 stage: -> patch review ___ Python tracker ___ ___

[issue24638] asyncio "loop argument must agree with future" error message could be improved

2018-09-22 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24638] asyncio loop argument must agree with future error message could be improved

2015-07-15 Thread R. David Murray
R. David Murray added the comment: This error message is in tasks.py. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24638 ___ ___

[issue24638] asyncio loop argument must agree with future error message could be improved

2015-07-15 Thread R. David Murray
New submission from R. David Murray: I just got the titular error message and had no idea what it meant until I looked at the source. It seems to mean the specified loop is different from the _loop attribute of the future-or-coroutine. Since _loop is nominally private, perhaps the message