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 vlad
Recipients berker.peksag, ghaering, rhettinger, terry.reedy, vlad
Date 2019-02-22.10:21:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550830897.09.0.724788003928.issue35889@roundup.psfhosted.org>
In-reply-to
Content
There is no need to add explicit knowledge of reprlib to the Row object or vice versa.

Those who use reprlib to limit output size will have no problem. Reprlib already truncates arbitrary reprs at the string level: https://github.com/python/cpython/blob/22bfe637ca7728e9f74d4dc8bb7a15ee2a913815/Lib/reprlib.py#L144

Those who use builtin repr() have to be prepared for the possibility of unbounded repr anyway, because all collection-like objects in Python have unbounded __repr__.

It would be annoying if some collection-like objects decided to be clever and omit parts of their regular __repr__ because they feel it's too much for the user to handle.
History
Date User Action Args
2019-02-22 10:21:37vladsetrecipients: + vlad, rhettinger, terry.reedy, ghaering, berker.peksag
2019-02-22 10:21:37vladsetmessageid: <1550830897.09.0.724788003928.issue35889@roundup.psfhosted.org>
2019-02-22 10:21:37vladlinkissue35889 messages
2019-02-22 10:21:36vladcreate