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 eric.snow
Recipients eric.snow, serhiy.storchaka, vstinner
Date 2013-11-20.05:12:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384924364.11.0.42084728954.issue19653@psf.upfronthosting.co.za>
In-reply-to
Content
As far as I'm aware, the performance of __repr__() for any object is not much of a concern.  Repr is mostly for debugging and interactive use, so it's already fast/efficient enough for the target consumers: us. :)  Making __repr__() easier to write or maintain is worth it as long as benefit outweighs the cost of the churn.
History
Date User Action Args
2013-11-20 05:12:44eric.snowsetrecipients: + eric.snow, vstinner, serhiy.storchaka
2013-11-20 05:12:44eric.snowsetmessageid: <1384924364.11.0.42084728954.issue19653@psf.upfronthosting.co.za>
2013-11-20 05:12:44eric.snowlinkissue19653 messages
2013-11-20 05:12:43eric.snowcreate