On 5/27/08, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Blake Winton wrote:
> > But which downsides do you see that aren't solved by the use of repr to > get unambiguous output? > The fact that calling str() on containers has been unambiguous for years. > All I'm saying is that no compelling use cases have been presented to > justify changing the status quo (aside from the Unicode escaping problem, > which is better addressed by allowing repr() to return arbitrary Unicode > glyphs as proposed by PEP 3138, since that also fixes a bunch of other cases > where repr() is invoked on Unicode strings). I think it is pretty clear that there are sometimes reasons to want more than one string representation. There are arguably far more than two distinctions that would be useful, but two is what the language supports. That was the justification for str vs repr in the first place. What is the advantage in continuing to conflate the two for (only portions of) containers? The only justfication that I can see is "backwards compatibility", which applies even more strongly to repr than it does to str. -jJ _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
