A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-April/034861.html below:

[Python-Dev] Re: ''.join() again

[Python-Dev] Re: ''.join() again [Python-Dev] Re: ''.join() againZack Weinberg zack@codesourcery.com
Mon, 21 Apr 2003 11:08:56 -0700
Barry Warsaw <barry@python.org> writes:

> OTOH, I wouldn't object too strenuously to a join() builtin, but I'd
> probably never use it -- I'm sure I'd rarely remember the argument order
> and hate having too look it up much more than writing out the current
> spelling.  Admit it: there is no natural unforgetable order! :)

It occurs to me that one may put

join = str.join

at the top of one's module, and thereafter use

join('str', sequence)

(For 2.1 backward compatibility, use type('') instead of str.)

Possibly this is a counterargument to accusations that a join builtin
would be bloat, since the same implementation could be used for both.

zw



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4