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, pitrou, vstinner
Date 2013-11-29.15:58:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385740739.23.0.981288335184.issue19833@psf.upfronthosting.co.za>
In-reply-to
Content
> Since there are many event loop methods, I structured the doc so that methods are grouped in different sections: see the existing "delayed calls" and "creating connections" sections.

Seriously, I read the documentation three times (HTML and the source), but I didn't notice that asyncio.call_later() is not a function, but a method of an object.

> I'm not saying it's the best solution (is it?), but I think it would be nice to be consistent :)

There are too many methods, it's a good solution. I will rewrite asyncio_doc_eventloop.patch to group the methods.

Before that, here is a patch to mention the class for methods.
History
Date User Action Args
2013-11-29 15:58:59vstinnersetrecipients: + vstinner, gvanrossum, pitrou, docs@python
2013-11-29 15:58:59vstinnersetmessageid: <1385740739.23.0.981288335184.issue19833@psf.upfronthosting.co.za>
2013-11-29 15:58:59vstinnerlinkissue19833 messages
2013-11-29 15:58:59vstinnercreate