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 ncoghlan
Recipients eric.araujo, eric.snow, ezio.melotti, gvanrossum, martin.panter, ncoghlan, pitrou, rbcollins, serhiy.storchaka, veky, vstinner
Date 2017-09-19.05:46:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505800018.33.0.643566907755.issue13224@psf.upfronthosting.co.za>
In-reply-to
Content
Specifically this message, where the unwritten rationale is to offer behavioural consistency across the builtin types that know their own name and include it in their current repr() output: https://mail.python.org/pipermail/python-ideas/2011-October/012464.html

As per Guido's comment and the discussion of PEP 3155 above, the idea now is that for classes/functions/methods, we make it so that:

repr(x) -> gives both the type and the qualified name (as now)
str(x) -> gives just the qualified name

Importantly, this *won't* change the result of printing full namespaces, since the dict repr calls repr() on values, not str().
History
Date User Action Args
2017-09-19 05:46:58ncoghlansetrecipients: + ncoghlan, gvanrossum, pitrou, vstinner, rbcollins, ezio.melotti, eric.araujo, eric.snow, martin.panter, serhiy.storchaka, veky
2017-09-19 05:46:58ncoghlansetmessageid: <1505800018.33.0.643566907755.issue13224@psf.upfronthosting.co.za>
2017-09-19 05:46:58ncoghlanlinkissue13224 messages
2017-09-19 05:46:57ncoghlancreate