Jesse Hersch wrote:
What is the usual way sage developers go about making changes in cython
code without rebuilding everything?
Edit the file(s), then run './sage -b' (which only rebuilds the
necessary files of the Sage library).
'./sage -br' rebuilds the library and afterwards starts Sage, such that
you can check the effects of your changes.
But before starting to modify the code, you should create a branch for
your work such that you can always easily switch back to a "clean"
version of Sage. See [1].
-leif
P.S.: Thanks for your very nice bug report!
[1]
http://sagemath.org/doc/developer/walk_through.html#starting-without-a-ticket
(as of now, still the documentation for Sage 6.1.1)
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
