➜

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 chris.jerdonek
Recipients chris.jerdonek, ezio.melotti, georg.brandl, gregory.p.smith, mark.dickinson, python-dev, serhiy.storchaka
Date 2012-12-28.10:36:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1356690987.16.0.0803455239378.issue16772@psf.upfronthosting.co.za>
In-reply-to
Content 
> I actually think this issue can be closed as fixed:  the current code looks fine to me, and I don't think the fix should be backported.

How about backporting the tests?  In addition to adding tests for the fix, Greg added more comprehensive tests for the existing behavior (i.e. test_int_base_limits()).  Backporting the latter would help prevent regressions from future fixes in earlier versions.

Also, if we don't backport shouldn't there be a version changed in the docs?
History
Date User Action Args
2012-12-28 10:36:27chris.jerdoneksetrecipients: + chris.jerdonek, georg.brandl, gregory.p.smith, mark.dickinson, ezio.melotti, python-dev, serhiy.storchaka
2012-12-28 10:36:27chris.jerdoneksetmessageid: <1356690987.16.0.0803455239378.issue16772@psf.upfronthosting.co.za>
2012-12-28 10:36:27chris.jerdoneklinkissue16772 messages
2012-12-28 10:36:26chris.jerdonekcreate