A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2007-March/071911.html below:

[Python-3000] Removing functions from the operator module

[Python-Dev] Fwd: Re: [Python-3000] Removing functions from the operator moduleArmin Rigo arigo at tunes.org
Mon Mar 12 21:17:24 CET 2007
Hi Collin,

On Mon, Mar 12, 2007 at 11:19:26AM -0500, Collin Winter wrote:
> iter() is part of every syntactic construction that takes an iterator
> argument (for, listcomps, gencomps, ...). Should it go in operator as
> well?

Historically, things that have a slot go in 'operator'.  So that would
mean that 'operator' is missing at least: getattr, setattr, delattr,
next, repr, str, len, hash, hex, oct, divmod, int, float, long,
descr_get, descr_set, descr_delete, getslice, setslice, delslice, call,
init.

Or else, things in 'operator' are the ones with a "syntactic
equivalent".  Then we should remove abs and index, and add list, tuple,
dict, buildclass, new.function, ...

Then there is stuff that doesn't fall in any category, like attrgetter, 
countOf, indexOf, ...


Not-completely-useful'y-yours,

Armin
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