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 terry.reedy
Recipients akuchling, docs@python, loewis, methane, r.david.murray, terry.reedy, tim.peters
Date 2010-05-14.19:10:58
SpamBayes Score 0.020666333
Marked as misclassified No
Message-id <1273864261.18.0.236753697541.issue8686@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with Tim. Drop the zero-info glosses. For real_quick_ratio(),
    "Return an upper bound on ratio() even more quickly."
should be sufficient (assuming that it *is* always quicker.

Just curious, The descriptions say ratio() <= quick_ratio() and ratio() <= very_quick_ratio. is it also guaranteed that quick_ratio() <= real_quick_ratio()? Or might one 'luck out' with a better answer from the faster method? (I can imagine either being true.)
History
Date User Action Args
2010-05-14 19:11:01terry.reedysetrecipients: + terry.reedy, tim.peters, loewis, akuchling, r.david.murray, methane, docs@python
2010-05-14 19:11:01terry.reedysetmessageid: <1273864261.18.0.236753697541.issue8686@psf.upfronthosting.co.za>
2010-05-14 19:10:59terry.reedylinkissue8686 messages
2010-05-14 19:10:58terry.reedycreate