Message 298380 - Python tracker

➜

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	chris.jerdonek
Recipients	chris.jerdonek, docs@python
Date	2017-07-15.02:03:41
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
In-reply-to

Content
Currently, the Python asyncio.get_event_loop() docs don't say that get_event_loop() returns the currently running event loop when it is called from a coroutine: https://docs.python.org/3/library/asyncio-eventloops.html#asyncio.get_event_loop https://docs.python.org/3/library/asyncio-eventloops.html#asyncio.AbstractEventLoopPolicy.get_event_loop This is new behavior that was introduced in Python 3.6 in this issue: https://github.com/python/asyncio/pull/452 Without this, the docs make it seem like get_event_loop() should return the loop that was last passed to set_event_loop(). This could be added with a "Changed in version 3.6" note.

Currently, the Python asyncio.get_event_loop() docs don't say that get_event_loop() returns the currently running event loop when it is called from a coroutine:

https://docs.python.org/3/library/asyncio-eventloops.html#asyncio.get_event_loop
https://docs.python.org/3/library/asyncio-eventloops.html#asyncio.AbstractEventLoopPolicy.get_event_loop

This is new behavior that was introduced in Python 3.6 in this issue:
https://github.com/python/asyncio/pull/452

Without this, the docs make it seem like get_event_loop() should return the loop that was last passed to set_event_loop().

This could be added with a "Changed in version 3.6" note.

History
Date	User	Action	Args
2017-07-15 02:03:41	chris.jerdonek	set	recipients: + chris.jerdonek, docs@python
2017-07-15 02:03:41	chris.jerdonek	set	messageid: <1500084221.73.0.556830879215.issue30935@psf.upfronthosting.co.za>
2017-07-15 02:03:41	chris.jerdonek	link	issue30935 messages
2017-07-15 02:03:41	chris.jerdonek	create