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-November/040511.html below:

[Python-Dev] Banishing apply(), buffer(), coerce(), and intern()

[Python-Dev] Banishing apply(), buffer(), coerce(), and intern()Gerrit Holl gerrit at nl.linux.org
Sat Nov 29 10:32:50 EST 2003
Barry Scott wrote:
> Is the `expr` worth banishing? I've never used it myself
> because of the chance of misreading `expr` vs. 'expr'.
> Isn't it a hard to read str()?

It's a hard-to-read repr(), actually.

Guido once published a list of Python regrets, which can be found at:
http://www.python.org/doc/essays/ppt/regrets/PythonRegrets.pdf

At page 5, it suggests to drop `...` for repr(...), so unless Guido
changed his mind (I don't think so), this is a deprecation-canddate as
well: as is callable() and input(), by the way.

yours,
Gerrit.

-- 
147. If she have not borne him children, then her mistress may sell her
for money.
          -- 1780 BC, Hammurabi, Code of Law
-- 
Asperger's Syndrome - a personal approach:
	http://people.nl.linux.org/~gerrit/english/

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