> On 3 Nov 2019, at 11:39, Chris Angelico <ros...@gmail.com> wrote: > > On Sun, Nov 3, 2019 at 9:34 PM Anders Hovmöller <bo...@killingar.net> wrote: >> >> >> >>>> On 3 Nov 2019, at 10:28, Steven D'Aprano <st...@pearwood.info> wrote: >>> >>> On Sun, Nov 03, 2019 at 12:23:02AM -0700, Brendan Barnwell wrote: >>> >>>> For the record, I have always thought that str.join should call str >>>> on all its arguments. The fact that it doesn't is really annoying. >>> >>> Given: >>> >>> values = ["Hello", b"World"] >>> >>> would you expect ' '.join(values) to return >>> >>> "Hello b'World'" >>> >>> because that's what you'll get calling str automatically. >> >> Side note! >> >> That misfeature of python 3 was one of the largest source of continuing bugs >> in production for us after we switched. >> > > What misfeature? The fact that str() is able to give a representation > for any object? That dates back a lot further than Python 3.0.
That's a bit overstating how good str(x) is. Mostly it just gives you the type and a memory address that is mostly useless. It could have done that with bytes. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/ZOHQRX7VCZCNPFCYQPL5VROJJYLHL2ES/ Code of Conduct: http://python.org/psf/codeofconduct/
