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

Showing content from https://mail.python.org/pipermail/python-dev/2006-July/067817.html below:

[Python-Dev] Bad interaction of __index__ and sequence repeat

• Previous message: [Python-Dev] Bad interaction of __index__ and sequence repeat
• Next message: [Python-Dev] Bad interaction of __index__ and sequence repeat
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Guido van Rossum wrote:

> In my recollection I tried to avoid this exact behavior. I wanted
> __index__() to just return the unclipped int or long value, but have a
> C API that clipped it for use in slice operations.

So is there still a chance to fix it?

--
Greg

• Previous message: [Python-Dev] Bad interaction of __index__ and sequence repeat
• Next message: [Python-Dev] Bad interaction of __index__ and sequence repeat
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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