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

[Python-Dev] Single- vs. Multi-pass iterability

[Python-Dev] Single- vs. Multi-pass iterability [Python-Dev] Single- vs. Multi-pass iterabilityGuido van Rossum guido@python.org
Thu, 11 Jul 2002 20:43:57 -0400
> The real reason to be able to introspect is so that you can handle both
> kinds.
> Even if you're willing to destroy the data by examining it, if you know you
> have a single-pass sequence, you might need to copy its elements into a
> multi-pass sequence (e.g. file.lines()) in order to get your work done.

Hm.  I think it's just as good to make it the responsibility of the
caller to pass a multi-iterable.  There could be a standard tool that
takes a single-iterable and produces a multi-iterable.

--Guido van Rossum (home page: http://www.python.org/~guido/)




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