#17851: Disable Cython caching until upstream fixes it
-------------------------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: closed
Priority: major | Milestone: sage-6.6
Component: build | Resolution: fixed
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers: Vincent
Report Upstream: Reported upstream. No | Delecroix
feedback yet. | Work issues:
Branch: | Commit:
ff8b9fd18562be12020ce35477e05044374d5683 | Stopgaps:
Dependencies: |
-------------------------------------------------+-------------------------
Changes (by embray):
* commit: ff8b9fd18562be12020ce35477e05044374d5683 =>
Comment:
Any word on this? I just changed branches in order to make one little
change, then changed back to my previous branch and now have to recompile
350 Cython modules that haven't changed except for their timestamps.
If Cython's built in caching is a no-go, what about a simple mechanism for
storing the hashes of Cython modules when they're compiled, so that Cython
modules can always be compared to the hash of at least the last version
that was compiled?
--
Ticket URL: <http://trac.sagemath.org/ticket/17851#comment:21>
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.