Author brett.cannon
Recipients asvetlov, brett.cannon, docs@python, ezio.melotti, giampaolo.rodola, gvanrossum, pitrou, vstinner, yselivanov
Date 2015-10-29.16:27:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446136047.84.0.7324888002.issue25501@psf.upfronthosting.co.za>
In-reply-to
Content
Once 3.4.4 launches the need to keep the docs synced with a version that doesn't support async/await goes away. And worrying about 3.3 isn't necessary since asyncio was added in 3.4.

So once 3.4.4 is released and we close the 3.4 branch to bugfixes can we update the docs in asyncio and add a note at the top saying the examples all use async/await from 3.5 and if you need 3.4 compatibility to please look at the 3.4 docs? Otherwise how long do you want to wait until we can start using async/await in the documentation? My worry is that people are going to blindly copy the examples and tweak them for their needs since the asyncio docs are a bit dense and thus just simply overlook the fact that async/await exists.
History
Date User Action Args
2015-10-29 16:27:27brett.cannonsetrecipients: + brett.cannon, gvanrossum, pitrou, vstinner, giampaolo.rodola, ezio.melotti, asvetlov, docs@python, yselivanov
2015-10-29 16:27:27brett.cannonsetmessageid: <1446136047.84.0.7324888002.issue25501@psf.upfronthosting.co.za>
2015-10-29 16:27:27brett.cannonlinkissue25501 messages
2015-10-29 16:27:27brett.cannoncreate