[Python-Dev] PEP 418 is too divisive and confusing and should be postponed (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Thu Apr 5 18:59:07 CEST 2012
- Previous message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Next message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
- Previous message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Next message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]