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 vstinner
Recipients docs@python, gvanrossum, pydanny, vstinner, yselivanov
Date 2014-07-31.09:04:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406797473.6.0.804797806084.issue22112@psf.upfronthosting.co.za>
In-reply-to
Content
> This has been fixed in 3.4.2, but shows up in the 3.4.1 documentation.

Well, I didn't want to change Python 3.4.1 documentation, but it looks like https://docs.python.org/3.4/ is updated after each commit into the 3.4 branch. For example, new asyncio functions added in 3.4.2 are already documented:

https://docs.python.org/3.4/library/asyncio-eventloop.html#asyncio.BaseEventLoop.create_task

I changeed all examples to use create_task() instaed of async() or the Task contructor:

changeset:   91609:66f06fbf8a2f
branch:      3.4
user:        Victor Stinner <victor.stinner@gmail.com>
date:        Tue Jul 08 12:39:10 2014 +0200
files:       Doc/library/asyncio-dev.rst Doc/library/asyncio-eventloop.rst Doc/library/asyncio-stream.r
description:
Update asyncio documentation

- Document the new create_task() method
- "Hide" the Task class: point to the create_task() method for interoperability
- Rewrite the documentation of the Task class
- Document the "Pending task destroyed"
- Update output in debug mode of examples in the dev section
- Replace Task() with create_task() in examples


Maybe I should revert this change in the 3.4 branch, but mention that Python 3.4.2 and 3.5 have a new create_task() which is now the recommanded way to schedule a coroutine (to create a task object).
History
Date User Action Args
2014-07-31 09:04:33vstinnersetrecipients: + vstinner, gvanrossum, pydanny, docs@python, yselivanov
2014-07-31 09:04:33vstinnersetmessageid: <1406797473.6.0.804797806084.issue22112@psf.upfronthosting.co.za>
2014-07-31 09:04:33vstinnerlinkissue22112 messages
2014-07-31 09:04:33vstinnercreate