So, Would I be correct in that, because of this regression in __repr__ behavior (elipsis instead of total information) from 2.x to 3.x, any tests that string compare __repr__ are now off? On Dec 26, 2015 11:37 AM, "Guido van Rossum" <guido@python.org> wrote:
--Guido (mobile) ---------- Forwarded message ---------- From: <python-ideas-owner@python.org> Date: Dec 26, 2015 9:33 AM Subject: Re: [Python-ideas] Unambiguous repr for recursive objects To: <gvanrossum@gmail.com> Cc:
Your message has been rejected, probably because you are not subscribed to the mailing list and the list's policy is to prohibit non-members from posting to it. If you think that your messages are being rejected in error, contact the mailing list owner at python-ideas-owner@python.org.
---------- Forwarded message ---------- From: Guido van Rossum <gvanrossum@gmail.com> To: Serhiy Storchaka <storchaka@gmail.com> Cc: Python-Ideas <python-ideas@python.org> Date: Sat, 26 Dec 2015 09:33:37 -0700 Subject: Re: [Python-ideas] Unambiguous repr for recursive objects
I disagree. We should not take this guideline too literally. The dots are easily understood and nobody has been fooled by a list containing an ellipsis yet. (Also, isn't the repr of an ellipsis the string 'Ellipsis'?)
--Guido (mobile)
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/