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 pr
> 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 "conf
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
> 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
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
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 change
