#7017: prime_range problem
-----------------------------+----------------------------------------------
Reporter: kevin.stueve | Owner: kevin.stueve
Type: defect | Status: positive_review
Priority: critical | Milestone:
Component: number theory | Keywords: prime_range, primes, prime number
theory, prime
Work_issues: | Author: Kevin Stueve
Upstream: N/A | Reviewer: William Stein, Tim Dumol
Merged: |
-----------------------------+----------------------------------------------
Changes (by newvalueoldvalue):
* reviewer: was => William Stein, Tim Dumol
* author: kevin.stueve => Kevin Stueve
Comment:
So I'm happy for the code with the alternate algorithm to go in -- but it
doesn't seem to address the segfault mentioned in the description. I'm
happy to fix that soon, but can someone open a new ticket for it so we
don't forget?
Also, unless I'm missing something, the second hunk in the referee patch
seems erroneous. I like the referee patch otherwise -- pretty
documentation is always great. :)
Kevin: for the record, we put human-readable names in Author: and
Reviewer:, not trac usernames. (Did William review this, or was he
intending to?)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7017#comment:11>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
