[Python-Dev] PEP 418 is too divisive and confusing and should be postponed (original) (raw)
Eric Snow ericsnowcurrently at gmail.com
Fri Apr 6 01:09:42 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 Apr 5, 2012 11:01 AM, "Guido van Rossum" <guido at python.org> wrote:
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.
+1
-eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120405/1b5f4f93/attachment.html>
- 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 ]