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 asvetlov
Recipients asvetlov, docs@python, hniksic, miss-islington, rhettinger, vstinner, yselivanov
Date 2019-09-15.17:51:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1568569868.28.0.1460977759.issue38178@roundup.psfhosted.org>
In-reply-to
Content
Raymond, sorry if I was so quick in applying.
The patch is very trivial and obvious.
I am pretty sure that Yuri and Victor approve it.

The PR doesn't fix a mistake, the code is still valid.
But we all changed our mind what is the loop role, should it be explicitly passed everywhere or not, etc.

At the time of the example creation explicit loop was safer, after Python 3.5.3 bugfx release the implicit loop became the idiomatic solution.

We use the implicit loop everywhere, 3.8 raises DeprecationWarning for passing the loop into certain API calls.
The PR just changes the example to follow our own recommendations.
History
Date User Action Args
2019-09-15 17:51:08asvetlovsetrecipients: + asvetlov, rhettinger, vstinner, hniksic, docs@python, yselivanov, miss-islington
2019-09-15 17:51:08asvetlovsetmessageid: <1568569868.28.0.1460977759.issue38178@roundup.psfhosted.org>
2019-09-15 17:51:08asvetlovlinkissue38178 messages
2019-09-15 17:51:08asvetlovcreate