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/2008-April/078679.html below:

[Python-Dev] string representation of range in 3.0

[Python-Dev] string representation of range in 3.0 [Python-Dev] string representation of range in 3.0Curt Hagenlocher curt at hagenlocher.org
Wed Apr 16 16:54:43 CEST 2008
On Wed, Apr 16, 2008 at 6:58 AM, Steve Holden <steve at holdenweb.com> wrote:
>
> If you consume values from the iterator to display them in the repr()
> where do you then propose to store them until the application wants
> them, and how do you distinguish between "real" and "repr" consumption
> of the values? "The next couple of elements" is a dangerous thing to use
> unless you don't mind them disappearing.

Not only that, but you'd have no idea what the performance
consequences of accessing the "next" object might be.

--
Curt Hagenlocher
curt at hagenlocher.org
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