Re: [sage-devel] Factoring for Fun and Profit
On Tuesday, May 10, 2022 at 1:46:55 PM UTC-7 Michael Orlitzky wrote: > Keep in mind also the recent thread about "make build". Many people > still believe that "sage -i" should be able to install python for them. This is not actually related because Sage needs a version of python as a build prerequisite. This is "sage-bootstrap-python". -- 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/daeff9d9-70fb-4381-8ea9-e296c9500689n%40googlegroups.com.
Re: [sage-devel] Proposal: Make "configure --enable-editable" the default in Sage 9.7
> On 12/05/2022, at 12:52, Matthias Koeppe wrote: > > On Wednesday, May 11, 2022 at 5:48:38 PM UTC-7 François Bissey wrote: > > On 12/05/2022, at 10:54, Matthias Koeppe wrote: > > In https://trac.sagemath.org/ticket/32406 I propose to change the default > > installation of Sage to use "configure --enable-editable". > > 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. > > End users who do not edit the sources will not notice any difference. > Then it is certainly the most sensible, because differentiating between develop and master is just a disaster waiting to happen. +1 -- 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/F77B27A1-0897-4819-9CF3-3C25883E5277%40gmail.com.
Re: [sage-devel] Proposal: Make "configure --enable-editable" the default in Sage 9.7
On Wednesday, May 11, 2022 at 5:48:38 PM UTC-7 François Bissey wrote: > > On 12/05/2022, at 10:54, Matthias Koeppe wrote: > > In https://trac.sagemath.org/ticket/32406 I propose to change the > default installation of Sage to use "configure --enable-editable". > > 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. End users who do not edit the sources will not notice any difference. -- 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/4f33a516-07fc-49b6-83f0-e9df70702124n%40googlegroups.com.
Re: [sage-devel] Proposal: Make "configure --enable-editable" the default in Sage 9.7
> On 12/05/2022, at 10:54, Matthias Koeppe 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.
Re: [sage-devel] Proposal: Make "configure --enable-editable" the default in Sage 9.7
On Wed, May 11, 2022 at 3:54 PM Matthias Koeppe
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 opinion is +1000! Finally! This is so much better.
William
>
> --
> 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.
--
William (http://wstein.org)
--
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/CACLE5GCYHm%3DT-FPgXcF1ZWxe6v3AWKNgqLyZB6Q-B%3DfMH4C2SA%40mail.gmail.com.
[sage-devel] Proposal: Make "configure --enable-editable" the default in Sage 9.7
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.
