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 pydanny
Recipients docs@python, gvanrossum, pydanny, vstinner, yselivanov
Date 2014-07-31.16:51:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406825492.88.0.379500360702.issue22112@psf.upfronthosting.co.za>
In-reply-to
Content
First, if there is documentation that says, "3.4.1", doesn't it make sense that the documentation should only be for 3.4.1? Which means that this create_task documentation should be reverted in the 3.4.1 documentation to match the 3.4.1 specification.

Second and most respectfully, why is a feature being added in 3.4.2? I thought this kind of release (3.4.1 to 3.4.2) was for bug fixes and security issues, not new features. Unless create_task was in the original 3.4 specification, I argue that create_task belongs in 3.5. In it's place, a recipe of running tasks in parallel fashion per gvanrossum's suggestion of asyncio.async() could be added.
History
Date User Action Args
2014-07-31 16:51:32pydannysetrecipients: + pydanny, gvanrossum, vstinner, docs@python, yselivanov
2014-07-31 16:51:32pydannysetmessageid: <1406825492.88.0.379500360702.issue22112@psf.upfronthosting.co.za>
2014-07-31 16:51:32pydannylinkissue22112 messages
2014-07-31 16:51:32pydannycreate