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

[Python-Dev] Deprecating obsolete builtins

[Python-Dev] Deprecating obsolete builtins [Python-Dev] Deprecating obsolete builtinsJeremy Hylton jeremy at alum.mit.edu
Wed Nov 5 16:06:40 EST 2003
On Wed, 2003-11-05 at 10:23, Guido van Rossum wrote:
> > Removing _any_ built-in that was around in 1.5.2 will pose similar
> > problems.
> 
> Only proportional to the likelihood that it was used in 1.5.2, which
> is proportional to how useful it is.  intern(): extremely unlikely
> (nobody knows what it's for); coerce(): rather unlikely (too
> advanced); apply(): very likely.

The solution is to get people to stop using 1.5.2.  I don't entirely
understand why so many people write new code that needs to work with it.

Jeremy




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