#20094: Fix and clean up xsrange
-------------------------------------+-------------------------------------
Reporter: dkrenn | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-7.1
Component: misc | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/xsrange_fails_with_large_inputs|
58d563a83521535df25373cbcdadd2d7d9a862c5
Dependencies: #20047 | Stopgaps:
-------------------------------------+-------------------------------------
Description changed by jdemeyer:
Old description:
> We have
> {{{
> sage: next(xsrange(0, 2^63-2^10+2^9))
> ...
> OverflowError: Python int too large to convert to C long
> }}}
> This is because the internally used variable `count` is too large.
>
> We solve this problem by avoiding `xrange()`. While we're at it, we also
> move `xsrange()` and related functions to a new Cython module
> `src/sage/arith/srange.pyx`.
New description:
We have
{{{
sage: next(xsrange(0, 2^63-2^10+2^9))
...
OverflowError: Python int too large to convert to C long
}}}
This is because the internally used variable `count` is too large. We
solve this problem by avoiding `xrange()`.
Besides this, we also move `xsrange()` and related functions to a new
Cython module `src/sage/arith/srange.pyx` and do some clean-up.
--
--
Ticket URL: <http://trac.sagemath.org/ticket/20094#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
