In https://trac.sagemath.org/ticket/32406 I propose to change the default 
installation of Sage to use "configure --enable-editable". 
This has many benefits for developers: If you only make changes to Python 
files, there is no need to rebuild ("sage -b"). Just restarting sage picks 
up the changes.
The only drawback may be for people who use a workflow that relies on the 
installed copy of Sage to be isolated from temporary edits by the fact that 
"sage -b" has not been run yet. (Moving the temporary edits out of the way 
using "git stash", using "configure --disable-editable", or using a second, 
stable copy/worktree of Sage are three ways to fix it.)
Opinions?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2cba7b80-04b6-4966-b483-0a2f19a03d33n%40googlegroups.com.

Reply via email to