➜

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 mark.dickinson
Recipients Leengit, mark.dickinson, rhettinger, serhiy.storchaka, zach.ware
Date 2022-02-17.19:08:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645124900.26.0.851176175687.issue46780@roundup.psfhosted.org>
In-reply-to
Content 
> I'd modify the optimization to be that we continue to seek the smallest denominator, but in the case that multiple numerators would give ratios within the computed interval then we choose the numerator among these that gives the ratio closest to the input value.

Hmm. This is getting more DWIM-like (Do What I Mean) by the minute. :-)

What about for an input of "0.001"? Your current specification would give 1/667, but I'm betting that you'd actually prefer 1/1000.
History
Date User Action Args
2022-02-17 19:08:20mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, zach.ware, serhiy.storchaka, Leengit
2022-02-17 19:08:20mark.dickinsonsetmessageid: <1645124900.26.0.851176175687.issue46780@roundup.psfhosted.org>
2022-02-17 19:08:20mark.dickinsonlinkissue46780 messages
2022-02-17 19:08:20mark.dickinsoncreate