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 gvanrossum
Recipients Nofar Schnider, Tim.Graham, Winterflower, abarry, brett.cannon, gvanrossum, kushal.das, martin.panter, matrixise, mbussonn, petere, ppperry, python-dev, rhettinger, terry.reedy
Date 2016-07-13.20:47:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJ+pe79JAi-AsWj0ariziDBThr1R6rKVMozuGYW3WdsUOg@mail.gmail.com>
In-reply-to <1468441450.07.0.119515949876.issue25548@psf.upfronthosting.co.za>
Content
Thanks, let's roll it back.

The reason it never was an issue for old-style classes is that they
behaved like this from the start, so nobody wrote tests that depended
on the predictability of repr(). But new-style classes have had this
nice clean repr() since they were introduced (in 2.3?) so it's
unsurprising that this is now depended upon.

Here's a link to some test code for mypy that broke:
https://github.com/python/mypy/blob/master/mypy/util.py#L22-L23

It may be irreprehensible code but it works for Python 3.2-3.5 (and
for new-style classes in Python 2, except mypy requires Python 3), and
broke in 3.6.
History
Date User Action Args
2016-07-13 20:47:37gvanrossumsetrecipients: + gvanrossum, brett.cannon, rhettinger, terry.reedy, petere, python-dev, martin.panter, kushal.das, matrixise, ppperry, Tim.Graham, mbussonn, abarry, Winterflower, Nofar Schnider
2016-07-13 20:47:36gvanrossumlinkissue25548 messages
2016-07-13 20:47:36gvanrossumcreate