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 cool-RR
Recipients cool-RR, terry.reedy, yselivanov
Date 2014-01-24.19:55:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390593333.35.0.81078754301.issue20378@psf.upfronthosting.co.za>
In-reply-to
Content
My impression is that the `__repr__` method of any object is intended to describe that object, hopefully in a succinct way, possibly in a REPL-friendly way (like `list.__repr__`  for example) but if not then at least human-friendly. This is for easy introspection. When I come across a Signature object in the shell, I want to immediately get a good feel for what it contains without exploring `vars(sig)` manully.

If you have a `Signature` object, why not have its `__repr__` return something like '<Signature f: alpha, beta=3, *args, **kwargs>`? This would do an awesome job at helping me understand what kind of signature object I'm looking at.
History
Date User Action Args
2014-01-24 19:55:33cool-RRsetrecipients: + cool-RR, terry.reedy, yselivanov
2014-01-24 19:55:33cool-RRsetmessageid: <1390593333.35.0.81078754301.issue20378@psf.upfronthosting.co.za>
2014-01-24 19:55:33cool-RRlinkissue20378 messages
2014-01-24 19:55:32cool-RRcreate