[Python-Dev] str(container) should call str(item), not repr(item) (original) (raw)
Matt Giuca matt.giuca at gmail.com
Mon Jul 28 12:58:05 CEST 2008
- Previous message: [Python-Dev] str(container) should call str(item), not repr(item)
- Next message: [Python-Dev] str(container) should call str(item), not repr(item)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Another disadvantage of calling str recursively rather than repr is that it places an onus on anyone writing a class to write both a repr and a str method (or be inconsistent with the newly-accepted standard for container types).
I personally write a repr method for most classes, which aids debugging. This means all my classes behave like containers currently do - their str will call repr on the items. This proposal will make all of my classes behave inconsistently with the standard container types.
- Matt Giuca -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20080728/188881f0/attachment.htm>
- Previous message: [Python-Dev] str(container) should call str(item), not repr(item)
- Next message: [Python-Dev] str(container) should call str(item), not repr(item)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]