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 belopolsky
Recipients belopolsky, eric.smith, ezio.melotti, lemburg, mark.dickinson, skrah, vstinner
Date 2010-12-03.02:53:36
SpamBayes Score 3.4401319e-06
Marked as misclassified No
Message-id <1291344829.29.0.413309910585.issue10557@psf.upfronthosting.co.za>
In-reply-to
Content
I am submitting a new patch that excludes int() changes.  The honest reason for the exclusion is that I gave up chasing a bug that only shows in full regrtest runs.  (Marc, I don't think it is related to what you thought was a missing norm decref: that place had result = NULL, not return NULL, so the contral was falling through to the decref after the if statement.)  Nevertheless, I think it makes sense to proceed with smaller steps.  As Marc suggested, PyUnicode_EncodeDecimal() API will stay indefinitely, so there is no urge to remove its use.  There are no actual bugs associated with int(), so technically it does not belong to this issue.
History
Date User Action Args
2010-12-03 02:53:49belopolskysetrecipients: + belopolsky, lemburg, mark.dickinson, vstinner, eric.smith, ezio.melotti, skrah
2010-12-03 02:53:49belopolskysetmessageid: <1291344829.29.0.413309910585.issue10557@psf.upfronthosting.co.za>
2010-12-03 02:53:36belopolskylinkissue10557 messages
2010-12-03 02:53:36belopolskycreate