Message304762
Since the appearance of reprs is not guaranteed. I don't think this should be documented (because doing so makes it a guaranteed behavior). In fact, the appearance has changed over time from ... to [...] in and may change at some point to <...> so that it can't be confused with an actual Ellipsis object. At best this should be a FAQ entry or we can defer to behaviors that are documented and guaranteed (such as reprlib.recursive_repr() and its default fillvalue).
I concur with David Murray that the Ellipsis object should be indexed and cross-referenced. |
|
Date |
User |
Action |
Args |
2017-10-22 21:18:51 | rhettinger | set | recipients:
+ rhettinger, terry.reedy, eric.araujo, r.david.murray, docs@python, vexoxev |
2017-10-22 21:18:50 | rhettinger | set | messageid: <1508707130.95.0.213398074469.issue9842@psf.upfronthosting.co.za> |
2017-10-22 21:18:50 | rhettinger | link | issue9842 messages |
2017-10-22 21:18:50 | rhettinger | create | |
|