> On 12/05/2022, at 10:54, Matthias Koeppe <matthiaskoe...@gmail.com> wrote:
>
> 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?
>
My first reaction was that it was a good idea. My view with a bit of reflection
is that most devs on this list will want that.
But not necessarily end users who just want to use sage.
With that in mind, I think the default should be editable on the development
branch but non-editable for stable release.
This is a mere opinion and there is certainly space to disagree and further may
prove unpractical.
François
--
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/511A51C0-3EAA-4EEC-9483-BFD721A7C803%40gmail.com.
