<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 20 May 2016, at 12:22, Guido van Rossum <<a href="mailto:guido@python.org" class="">guido@python.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">OK, I finally see the point. There are legitimate situations where<br class="">get_event_loop() returns None (this is how most of asyncio's tests are<br class="">running). </div></blockquote><div><br class=""></div>Unless there are tests that expect that get_event_loop() would return None</div><div class="">when called from within coroutine it should be fine.<br class=""><div><br class=""></div><blockquote type="cite" class="">So we want a separate function, e.g.<br class="">get_current_event_loop(). Send a PR to the GitHub project.<br class=""></blockquote><br class=""></div><div class="">Also see related bug: <a href="http://bugs.python.org/issue26969" class="">http://bugs.python.org/issue26969</a></div><div class="">Yuri did some work, but he argumented in favor of modifying get_event_loop.</div><div class=""><br class=""></div><div class="">Should we continue discussion of implementation here or in that issue?</div><div class=""><br class=""></div></body></html>