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 serhiy.storchaka
Recipients Dave Hibbitts, RazerM, eryksun, georg.brandl, mark.dickinson, paul.moore, pitrou, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-02-24.15:42:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <42835982.u32zig0k74@xarax>
In-reply-to <>
> 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.

What about xrange(-1, 2**31-1)? In any case the fact that xrange works not 
with Py_ssize_t, but with long, looks as a bug. I'll open a separate issue for 

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

I see that the sq_length slot in the weakproxy type is set to proxy_length.
Date User Action Args
2016-02-24 15:42:43serhiy.storchakasetrecipients: + serhiy.storchaka, georg.brandl, paul.moore, mark.dickinson, pitrou, vstinner, tim.golden, zach.ware, eryksun, steve.dower, RazerM, Dave Hibbitts
2016-02-24 15:42:43serhiy.storchakalinkissue26423 messages
2016-02-24 15:42:43serhiy.storchakacreate