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 stutzbach
Recipients belopolsky, mark.dickinson, rhettinger, stutzbach
Date 2010-05-12.01:00:35
SpamBayes Score 0.000607586
Marked as misclassified No
Message-id <>
In-reply-to <>
On Tue, May 11, 2010 at 7:15 PM, Alexander Belopolsky
<> wrote:
> The main value in setting a theoretically justified limit is that
> overflow exception can carry a meaningful message, e.g. "factorial
> result would have too many digits", rather than an unhelpful "Python
> int too large to convert to C long".

I'm pretty sure this is an orthogonal issue to speeding up
math.factorial.  If you want to improve the error and/or impose a
tighter maximum limit on n, would you mind opening it as a separate

I like extra checks and I like speed, but I can't think about adding
extra checks and a speed patch at the same time. ;-)
Date User Action Args
2010-05-12 01:00:44stutzbachsetrecipients: + stutzbach, rhettinger, mark.dickinson, belopolsky
2010-05-12 01:00:42stutzbachlinkissue8692 messages
2010-05-12 01:00:36stutzbachcreate