#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 jdemeyer):
Replying to [comment:3 rws]:
> Replying to [comment:2 jdemeyer]:
> > If the Cython version number was touched, it means that Cython really
changed (otherwise, we wouldn't have changed the Cython version
number...). So I don't really understand the issue.
> Maybe I'm stupid but somewhere the dependencies are described, e.g., in
a Makefile or other config, which trigger the complete build. Instead, you
trigger it when the version string changes, not when the timestamp
changes. This results in identical behaviour on upgrade, but spares full
recythonize when I do an old branch checkout followed by develop merge.
???
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).
--
Ticket URL: <http://trac.sagemath.org/ticket/18256#comment:4>
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.
