#16777: Track pyx files in citation modules/ reorganize it
-------------------------------------+-------------------------------------
Reporter: mraum | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: misc | Resolution:
Keywords: | Merged in:
Authors: Martin Raum | Reviewers: Volker Braun
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/mraum/ticket/16777 | b423bfee14e0799831aa5584b917b54eb80c2a7d
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by mraum):
* commit: 7964470c314603a36795169b2348220a6c34a7f5 =>
b423bfee14e0799831aa5584b917b54eb80c2a7d
Comment:
This implements the approach that was suggested by Volker, reasoning that
branch prediction will avoid slow down in critical (e.g. Cython or C)
code. The test suite runs, on my computer, 1.3% slower. I have also tested
a more critical part, sage/rings, which runs 2.8% slower.
See https://groups.google.com/d/msg/sage-devel/xoPszCcMtns/Y5UYdOr-WVsJ
for a discussion. As a remark, I want to say also here: If we want to have
citations (which I strongly believe is a question of publication ethics),
either we need the profiling approach (which does not interoperate well
with the Sage ecosystem) or we have to accept a minor slow down.
--
Ticket URL: <http://trac.sagemath.org/ticket/16777#comment:24>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.