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

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

[Python-Dev] Banishing apply(), buffer(), coerce(), and intern()Barry Scott barry at barrys-emacs.org
Sat Nov 29 09:50:38 EST 2003
At 28-11-2003 19:49, you wrote:
>Raymond Hettinger wrote:
> > Date: Tue, 25 Nov 2003 07:26:15 +0100
>
> > After re-reading previous posts on the subject, I had an idea.  Let's
> > isolate these functions in the documentation into a separate section
> > following the rest of the builtins.

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()?

Note: I tried to find it in the language reference and its not in the index
but then neither is %.

Barry



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