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/2005-March/052226.html below:

[Python-Dev] Rationale for sum()'s design?

[Python-Dev] Rationale for sum()'s design? [Python-Dev] Rationale for sum()'s design?Guido van Rossum gvanrossum at gmail.com
Wed Mar 16 17:26:39 CET 2005
> I guess that leaves Alex's question of whether or not supplying a string of some
> description as the initial value can be legitimately translated to:
> 
>    if isinstance(initial, basestring):
>      return initial + type(initial)().join(seq)

If you're trying to get people in the habit of writing sum(x, "")
instead of "".join(x), I fear that they'll try sum(x, " ") instead of
" ".join(x), and be sadly disappointed.

Frankly, I've had enough of this exploration of alternative
definitions for sum(), and think it is perfect as it is.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-Dev mailing list

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