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

* (and **?) in assignments

[Python-Dev] Half-baked proposal: * (and **?) in assignments [Python-Dev] Half-baked proposal: * (and **?) in assignmentsBrett Cannon bac@OCF.Berkeley.EDU
Sun, 24 Nov 2002 01:40:45 -0800 (PST)
[Oren Tirosh]

> I like this function, but the argument name is misleading - it isn't
> necessarily an iterator. In the common use cases it will be a list or
> tuple.
>
> def peel(iterable, arg_cnt=2):
>     iterator = iter(iterable)
>     for num in xrange(arg_cnt):
>         yield iterator.next()
>     yield iterator
>
> The name 'iterable' is unambigous but a little awkward. I'd like to
> use the term 'sequence' but I'm afraid people already associate it
> with the built-in sequence types or with something indexable rather
> than iterable. Do you think of iterators as a sequences?
>

I know I think of them as a lazy sequence.  But you are right, people tend
to associate sequence with either lists or tuples, perhaps because you can
do indexing on them.

-Brett




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