Tim Peters added the comment:
Thanks for the effort, but I'm rejecting this. The language deliberately defines nothing about how these are calculated. It defines how `.ratio()` is computed, but that's all. An implementation is free to do whatever it likes for the "quick" versions, provided only they return upper bounds on `.ratio()`. Indeed, it's perfectly fine if an implementation merely returns 1.0 for both, regardless of the arguments.
If an implementation is cleverer than that, great, that's fine too - but it would be actively counterproductive to constrain them to be no _more_ clever than the current implementations.
----------
nosy: +tim.peters
resolution: -> rejected
stage: patch review -> resolved
status: open -> closed
_______________________________________
Python tracker
https://bugs.python.org/issue40539
_______________________________________