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 matpi
Recipients ezio.melotti, matpi, mrabarnett, serhiy.storchaka, xtreak
Date 2020-06-16.09:59:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592301548.19.0.12788353505.issue40984@roundup.psfhosted.org>
In-reply-to
Content
Pardon me, but I see an important difference with the other bug report: that one is about a repr in angle brackets, and as such does not require an exact output, so an ellipsis is good enough.

In this bug, the output of repr gives a string than can, at least for small enough patterns, be passed to eval() to recontruct an object. So there is no good reason that this can be done for patterns up to 200 characters but not above; furthermore it is undocumented and goes against the doc on repr.

Compare with a complexly-nested structure of, say, lists, dicts and strings: The repr will always be "reconstructible", even if it is well above 200 characters.

Also, a common way to write repr is to draw the outer "container" as a string, and fill it with the (full!) repr of the object's parameters. E.g. the repr of a list containing a 1000-character string will simply write square brackets around the 1002-character repr of the string. re.compile doesn't conform to this "rule".
History
Date User Action Args
2020-06-16 09:59:08matpisetrecipients: + matpi, ezio.melotti, mrabarnett, serhiy.storchaka, xtreak
2020-06-16 09:59:08matpisetmessageid: <1592301548.19.0.12788353505.issue40984@roundup.psfhosted.org>
2020-06-16 09:59:08matpilinkissue40984 messages
2020-06-16 09:59:08matpicreate