Message 361249 - 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	serhiy.storchaka
Recipients	asvetlov, serhiy.storchaka, yselivanov
Date	2020-02-02.17:12:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
Yes, it is what I meant. Many code written before 3.7 use get_event_loop() because there was no get_running_loop() yet. Now, to avoid deprecation (and making the code more robust) it should be rewritten with using get_running_loop() or get_event_loop() depending on Python version. It is cumbersome, and causes a code churn.

Yes, it is what I meant.

Many code written before 3.7 use get_event_loop() because there was no get_running_loop() yet. Now, to avoid deprecation (and making the code more robust) it should be rewritten with using get_running_loop() or get_event_loop() depending on Python version. It is cumbersome, and causes a code churn.

History
Date	User	Action	Args
2020-02-02 17:12:57	serhiy.storchaka	set	recipients: + serhiy.storchaka, asvetlov, yselivanov
2020-02-02 17:12:56	serhiy.storchaka	set	messageid: <[email protected]>
2020-02-02 17:12:56	serhiy.storchaka	link	issue39529 messages
2020-02-02 17:12:56	serhiy.storchaka	create