Author bar.harel
Recipients David MacIver, bar.harel, steven.daprano
Date 2015-09-19.15:08:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442675325.32.0.978351904792.issue25177@psf.upfronthosting.co.za>
In-reply-to
Content
Whoop! I see the reason for it now. By limit I don't mean the precision limit, I mean the top limit in which float converts to "inf".
Seems like this bug is due to the change of python 3's division operator.
Under numbers it states:
"It's important that this conversion use the integer's "true"
division rather than casting one side to float before dividing
so that ratios of huge integers convert without overflowing."

It is meant to not to overflow but the "/" operator is now "//".
Lemme patch it up and see if it fixes the problem. If it states the integer's "true" division, I believe this small fix will be sufficient as it has been tested before.
History
Date User Action Args
2015-09-19 15:08:45bar.harelsetrecipients: + bar.harel, steven.daprano, David MacIver
2015-09-19 15:08:45bar.harelsetmessageid: <1442675325.32.0.978351904792.issue25177@psf.upfronthosting.co.za>
2015-09-19 15:08:45bar.harellinkissue25177 messages
2015-09-19 15:08:44bar.harelcreate