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.araujo
Recipients eric.araujo, rhettinger
Date 2010-09-13.00:13:06
SpamBayes Score 1.1554232e-07
Marked as misclassified No
Message-id <1284336789.64.0.524320834744.issue9840@psf.upfronthosting.co.za>
In-reply-to
Content
Good idea.  I wonder if the genericity (being able to specify the placeholder) is needed; the ellipsis is used by built-in containers (not documented AFAICT, see #9842) and seems a good choice for most (all?) of the cases.  What bothers me is that this simple, common case can’t just use @recursive_repr (without parens) which seems to me more natural.

One markup glitch: :meth:`repr__` lacks two underscores.

(Unimportant side question:  Since collections defines __all__, why are imported names renamed with a trailing underscore?)
History
Date User Action Args
2010-09-13 00:13:10eric.araujosetrecipients: + eric.araujo, rhettinger
2010-09-13 00:13:09eric.araujosetmessageid: <1284336789.64.0.524320834744.issue9840@psf.upfronthosting.co.za>
2010-09-13 00:13:08eric.araujolinkissue9840 messages
2010-09-13 00:13:06eric.araujocreate