A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/118524.html below:

[Python-Dev] PEP 418 is too divisive and confusing and should be postponed

[Python-Dev] PEP 418 is too divisive and confusing and should be postponed [Python-Dev] PEP 418 is too divisive and confusing and should be postponedAntoine Pitrou solipsis at pitrou.net
Thu Apr 5 18:59:07 CEST 2012
On Thu, 5 Apr 2012 09:56:19 -0700
Guido van Rossum <guido at python.org> wrote:
> 
> > For timeout purposes in a single process, such a clock is useful.  It just
> > isn't suitable for benchmarks, or for interprocess coordination.
> 
> I think it would be better if the proposed algorithm (or whatever
> algorithm to "fix" timeouts) was implemented by the
> application/library code using the timeout (or provided as a separate
> library function), rather than by the clock, since the clock can't
> know what fallback behavior the app/lib needs.

Agreed with providing it as a separate library function.

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4