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 casevh
Recipients belopolsky, casevh, pitrou, rhettinger, skrah
Date 2014-09-20.16:39:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANerV6mr0xoxRj_Njqv4r49HB=YXpgnQMqZLvG4zCKX=+HU1fA@mail.gmail.com>
In-reply-to <1411228889.28.0.752055468204.issue22444@psf.upfronthosting.co.za>
Content
> What are the use-cases for float // float where integer result is not acceptable?

It can lead to unexpected memory consumption when dealing with
arbitrary precision values. What should Decimal('1e123456')//1 return?
The result is exactly equal to Decimal('1e123456') but the
corresponding Python integer will consume ~55KB of RAM.

I'm also concerned that returning a very large integer will lead users
to assume that the result is more precise than it really is. Assuming
standard 64-bit double format, only the first 53 bits are significant.
All the remaining bits are 0.

>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue22444>
> _______________________________________
History
Date User Action Args
2014-09-20 16:39:28casevhsetrecipients: + casevh, rhettinger, belopolsky, pitrou, skrah
2014-09-20 16:39:28casevhlinkissue22444 messages
2014-09-20 16:39:28casevhcreate