[issue34815] Change Py_Ellipse __str__ behavior.

2018-09-27 Thread tom.r
tom.r added the comment: That's understandable. Thanks for considering it, closing the patch. -- stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/i

[issue34815] Change Py_Ellipse __str__ behavior.

2018-09-27 Thread tom.r
tom.r added the comment: Yes. I wanted to change just __str__ because the string value of an Ellipsis should be, well, an ellipsis. The __repr__ representation helps distinguish between recursion and an ellipsis object, so that's fine the way

[issue34815] Change Py_Ellipse __str__ behavior.

2018-09-27 Thread tom.r
tom.r added the comment: Frankly, because it bothered me that ``...`` evaluates to ``Ellipsis`` but that ``Ellipsis`` could never print as ``...``. -- ___ Python tracker <https://bugs.python.org/issue34

[issue34815] Change Py_Ellipse __str__ behavior.

2018-09-27 Thread tom.r
Change by tom.r : -- keywords: +patch pull_requests: +8994 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34815> ___ ___ Python-

[issue34815] Change Py_Ellipse __str__ behavior.

2018-09-27 Thread tom.r
New submission from tom.r : Added ellipsis_str function to Objects/sliceobject.c such that str(Ellipsis)=='...'. -- components: Interpreter Core files: sliceobject.c messages: 326522 nosy: photofone priority: normal severity: normal status: open title: Change Py_Ellipse __str__