[issue31950] Default event loop policy doc lacks precision

Antoine Pitrou added the comment: New changeset e65617f65e203a2a6d3e3100d0d6fed0ffa0613d by Antoine Pitrou (Miss Islington (bot)) in branch '3.6': bpo-31950: Improve event loop policy doc (GH-4306) (#4307)

[issue31950] Default event loop policy doc lacks precision

Antoine Pitrou added the comment: Thank you Guido. This is fixed now. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31950] Default event loop policy doc lacks precision

Change by Roundup Robot : -- pull_requests: +4270 ___ Python tracker ___

[issue31950] Default event loop policy doc lacks precision

Antoine Pitrou added the comment: New changeset 4135c89395726024abddb7340a0c7a42c801f616 by Antoine Pitrou in branch 'master': bpo-31950: Improve event loop policy doc (#4306) https://github.com/python/cpython/commit/4135c89395726024abddb7340a0c7a42c801f616 --

[issue31950] Default event loop policy doc lacks precision

Change by Antoine Pitrou : -- keywords: +patch pull_requests: +4269 stage: -> patch review ___ Python tracker ___

[issue31950] Default event loop policy doc lacks precision

Guido van Rossum added the comment: Agreed that this needs more clarification. Is something stopping you from submitting a PR? Note that the thing about non-main-threads is mentioned in the docstring for BaseDefaultEventLoopPolicy. I agree that the best way to create a new

[issue31950] Default event loop policy doc lacks precision

New submission from Antoine Pitrou : The doc for the default event loop policy states that """the default policy defines context as the current thread, and manages an event loop per thread that interacts with asyncio""". What it doesn't mention, though, is that you get a