#20210: Move memory functions to cysignals
-------------------------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: sage-7.1
Component: packages: standard | Resolution: fixed
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers: Martin
Report Upstream: N/A | Albrecht
Branch: | Work issues:
4bb8337295ed82c93d1a9c9f7173a4c36f97151d | Commit:
Dependencies: | Stopgaps:
-------------------------------------------------+-------------------------
Comment (by jdemeyer):
Replying to [comment:16 aly.deines]:
> I thought I only needed to run make when spkg changed
That is still true.
However: most of the time this spkg change is implicit when changing
branches. When you move from a branch based on one Sage version to a
branch based on a different Sage version, chances are high that some spkg
has changed between those branches.
> Should I more generally run make?
At least when changing branches, yes. Once you did this and you then make
changes only to the Sage library, then `./sage -b` should be sufficient.
But run `make` when in doubt.
Note that you can also use `make build` instead of `make` to skip the
documentation build which can take a while.
--
Ticket URL: <http://trac.sagemath.org/ticket/20210#comment:17>
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.
