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 vajrasky
Recipients mark.dickinson, python-dev, serhiy.storchaka, vajrasky, vstinner
Date 2013-08-05.13:39:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375709969.51.0.403840413799.issue18659@psf.upfronthosting.co.za>
In-reply-to
Content
For the passers-by who want to help:

The "precision too big" exception is raised in Python/formatter_unicode.c line 1168 and 1002.

The "Too many decimal digits..." exception is raised in Python/formatter_unicode.c line 71.

So the question is whether it is beneficial to differentiate the exception message. If not, we can change the exception message or test whether the digit passes INT_MAX first before checking with sys.max_size. If yes, we need to add test case for sys.max_size and use _testcapi.INT_MAX for current unit test case.
History
Date User Action Args
2013-08-05 13:39:29vajraskysetrecipients: + vajrasky, mark.dickinson, vstinner, python-dev, serhiy.storchaka
2013-08-05 13:39:29vajraskysetmessageid: <1375709969.51.0.403840413799.issue18659@psf.upfronthosting.co.za>
2013-08-05 13:39:29vajraskylinkissue18659 messages
2013-08-05 13:39:29vajraskycreate