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 tim.peters
Recipients christian.heimes, gregory.p.smith, mark.dickinson, tim.peters
Date 2013-08-15.18:38:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1376591904.0.0.366893084428.issue18739@psf.upfronthosting.co.za>
In-reply-to
Content
+1 on fixing it in 2.7, for the reasons Mark gave.

Way back when I introduced the original scheme, log(a_long) raised an exception, and the `int` and `long` types had a much higher wall between them.  The original scheme changed an annoying failure into a "pretty good" approximation, and because int operations never returned a long back then the relatively rare code using longs forced their use.

In the meantime, you can change failing cases of log(some_long) to log(int(some_long)).  int(some_long) will convert to int if possible (avoiding this path in the log code), but return some_long unchanged otherwise.  In the old days, int(some_long) would fail if some_long was too big to fit in an int - that's different now too - and for the better :-)
History
Date User Action Args
2013-08-15 18:38:24tim.peterssetrecipients: + tim.peters, gregory.p.smith, mark.dickinson, christian.heimes
2013-08-15 18:38:24tim.peterssetmessageid: <1376591904.0.0.366893084428.issue18739@psf.upfronthosting.co.za>
2013-08-15 18:38:23tim.peterslinkissue18739 messages
2013-08-15 18:38:23tim.peterscreate