#18256: recythonize only if cython really changed
-------------------------------+------------------------
Reporter: rws | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.7
Component: cython | Resolution:
Keywords: cythonize | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+------------------------
Comment (by rws):
Replying to [comment:4 jdemeyer]:
> I really don't understand what you are saying. Could you please clearly
indicate ''the problem'' (not an analysis or a fix, just the problem).
I frequently checkout older branches to do a fix or a review. After
checkout I often merge develop. Now when I `make`, due to (my guess) the
change back and forth in cython version a full recythonize is triggered.
But it is IMHO not necessary because I merged develop and so, only some
Python code really changed, or only specific `pyx` files. The proposal
here is to optimize the `make` behaviour in such cases.
--
Ticket URL: <http://trac.sagemath.org/ticket/18256#comment:5>
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.
