Message 302727 - Python tracker

➜

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	germn, pitrou, r.david.murray, vstinner, yselivanov
Date	2017-09-21.21:35:06
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<5d2261ae-35ea-0c37-b948-64557f8fc189@free.fr>
In-reply-to	<CAMpsgwY-mwQ87u0UK51-daZxO-1D5fWFtCM92agogoPs7dgJ5Q@mail.gmail.com>

Content
Le 21/09/2017 à 23:31, STINNER Victor a écrit : > > Yury: asyncio can trigger events earlier than scheduled for performance > reasons. If that's true, then it sounds like a bug. If there is a rationale for a "fast and imprecise" API, then it would seem ok to add such an API. But the default API for event scheduling should not take such shortcuts IMHO. Most users don't schedule thousands of events at a time, however they expect timeouts to be observed as rigorously as is possible given the usual implementation constraints such as GC pauses.

Le 21/09/2017 à 23:31, STINNER Victor a écrit :
> 
> Yury: asyncio can trigger events earlier than scheduled for performance
> reasons.

If that's true, then it sounds like a bug.  If there is a rationale for
a "fast and imprecise" API, then it would seem ok to add such an API.
But the default API for event scheduling should not take such shortcuts
IMHO.  Most users don't schedule thousands of events at a time, however
they expect timeouts to be observed as rigorously as is possible given
the usual implementation constraints such as GC pauses.

History
Date	User	Action	Args
2017-09-21 21:35:06	pitrou	set	recipients: + pitrou, vstinner, r.david.murray, yselivanov, germn
2017-09-21 21:35:06	pitrou	link	issue31539 messages
2017-09-21 21:35:06	pitrou	create