This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author benjamin.peterson
Recipients belopolsky, benjamin.peterson, facundobatista, gvanrossum, terry.reedy
Date 2008-05-02.23:11:55
SpamBayes Score 0.0022547566
Marked as misclassified No
Message-id <1afaf6160805021611x5c10b42ao67a16b8e794d0865@mail.gmail.com>
In-reply-to <1209768362.53.0.551189728746.issue2735@psf.upfronthosting.co.za>
Content
On Fri, May 2, 2008 at 5:46 PM, Guido van Rossum <report@bugs.python.org> wrote:
>
>  Guido van Rossum <guido@python.org> added the comment:
>
>  We need to look at more details why those fail.  Perhaps there's one
>  common place where this is used?  Did you add __length_hint__ yet?

I added __length_hint__ in the last patch.

Many of the failures are the result of failings in seq_tests.py.

As test_random points out, you can't pick a random integer from a set.

Some of these failures are also the result of removing range slicing.
(I'm not proposing we bring that back, though.)

Overall though, I think it's more practical to have a length
implementation that works in 99.78% cases than not and force people to
to convert it to a list first.
History
Date User Action Args
2008-05-02 23:11:57benjamin.petersonsetspambayes_score: 0.00225476 -> 0.0022547566
recipients: + benjamin.peterson, gvanrossum, terry.reedy, facundobatista, belopolsky
2008-05-02 23:11:55benjamin.petersonlinkissue2735 messages
2008-05-02 23:11:55benjamin.petersoncreate