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 vstinner
Recipients eli.bendersky, python-dev, scoder, serhiy.storchaka, vstinner
Date 2016-12-28.22:12:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwayDm5uE-VsmvFYTM5uPk8S7VE6XRiKLRVDdokD2nPZ7Q@mail.gmail.com>
In-reply-to <1482909194.16.0.445585773319.issue28871@psf.upfronthosting.co.za>
Content
This issue seems theorical to me, whereas the breakage of benchmarks is
very concrete for me. So I suggest to revert the change in Python 2.7.

(2) looks like the right design and it was implemented in Python 3 (no?).

I don't think that it's worth it to backport the change to Python 2. You
are the first one to report the issue and the backport is risky.
History
Date User Action Args
2016-12-28 22:12:13vstinnersetrecipients: + vstinner, scoder, eli.bendersky, python-dev, serhiy.storchaka
2016-12-28 22:12:12vstinnerlinkissue28871 messages
2016-12-28 22:12:12vstinnercreate