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 pitrou
Recipients docs@python, gvanrossum, pitrou, vstinner
Date 2013-11-29.15:22:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385738529.03.0.10815753334.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.

I'm not saying it's the best solution (is it?), but I think it would be nice to be consistent :)
History
Date User Action Args
2013-11-29 15:22:09pitrousetrecipients: + pitrou, gvanrossum, vstinner, docs@python
2013-11-29 15:22:09pitrousetmessageid: <1385738529.03.0.10815753334.issue19833@psf.upfronthosting.co.za>
2013-11-29 15:22:09pitroulinkissue19833 messages
2013-11-29 15:22:08pitroucreate