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 vstinner
Recipients Dave Hibbitts, RazerM, georg.brandl, mark.dickinson, paul.moore, pitrou, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-02-24.14:59:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456325988.79.0.360045497401.issue26423@psf.upfronthosting.co.za>
In-reply-to
Content
> Could we use the xrange() object for testing?

xrange() constructor is implemented in C and looks to use C long for parameters. This issue is specific to 64-bit Windows with 32-bit C long, so xrange() doesn't seem to work here.


> Or weakref?

What do you mean? Which object? weakref.ref() has no length.


> Using a bigmem test for this issue looks excessive.

Well, I was too lazy to develop a C extension (add something to _testcapi) just for this tiny bug.

I also like tests really testing the final feature (the bug reported in this issue).

I failed to find an existing Python object with __len__() implemented in C which doesn't need to allocate 2^31 bytes to test this bug.
History
Date User Action Args
2016-02-24 14:59:48vstinnersetrecipients: + vstinner, georg.brandl, paul.moore, mark.dickinson, pitrou, tim.golden, zach.ware, serhiy.storchaka, steve.dower, RazerM, Dave Hibbitts
2016-02-24 14:59:48vstinnersetmessageid: <1456325988.79.0.360045497401.issue26423@psf.upfronthosting.co.za>
2016-02-24 14:59:48vstinnerlinkissue26423 messages
2016-02-24 14:59:48vstinnercreate