➜

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 Marco Sulla
Recipients Marco Sulla, asvetlov, yselivanov
Date 2020-02-23.16:00:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582473604.21.0.900594119566.issue39698@roundup.psfhosted.org>
In-reply-to
Content 
I see that many breaking changes was done in recent releases. I get only the ones for `asyncio` in Python 3.8:

https://bugs.python.org/issue36921
https://bugs.python.org/issue36373
https://bugs.python.org/issue34790
https://bugs.python.org/issue32528
https://bugs.python.org/issue34687
https://bugs.python.org/issue32314

So I suppose the ship isn't sailed yet.


Passing a negative number to a function that should sleep the task for x seconds is a mistake. And mistakes should never pass silently.

Furthermore, coherence matters. It's really confusing that two functions in two builtin modules that are quite identical have a different behavior.

IMHO, deprecating and then removing support for negative argument in `asyncio.sleep()` is very much less breaking compared to issues #36921 and #36373 .
History
Date User Action Args
2020-02-23 16:00:04Marco Sullasetrecipients: + Marco Sulla, asvetlov, yselivanov
2020-02-23 16:00:04Marco Sullasetmessageid: <1582473604.21.0.900594119566.issue39698@roundup.psfhosted.org>
2020-02-23 16:00:04Marco Sullalinkissue39698 messages
2020-02-23 16:00:03Marco Sullacreate