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 steven.daprano
Recipients python-dev, serhiy.storchaka, steven.daprano, vstinner
Date 2014-07-22.11:48:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20140722114800.GP9112@ando>
In-reply-to <1406019042.04.0.51382116159.issue22031@psf.upfronthosting.co.za>
Content
> Many specialized reprs follow a pattern <... at {hexadecimal id}...>. 
> But there are few deviations:
[...]
> Proposed patch makes these cases to conform with other reprs.

I oppose making this change. The exact format of this generic repr of 
instances is not a part of Python's API, and we should not encourage 
people to think that it must always follow the same pattern or rely on 
that pattern.

Changing the repr risks breaking doctests. That *might* be acceptable if 
there was some obvious benefit to the change, e.g. changing from some 
generic <whatever at some_id> to a nicer, more useful display. But to 
risk breaking doctests just for consistency with other generic displays 
when that consistency has never been promised is not worth it.
History
Date User Action Args
2014-07-22 11:48:07steven.dapranosetrecipients: + steven.daprano, vstinner, python-dev, serhiy.storchaka
2014-07-22 11:48:07steven.dapranolinkissue22031 messages
2014-07-22 11:48:07steven.dapranocreate