On Mon, 2022-01-17 at 18:35 -0800, Matthias Koeppe wrote:
> On Monday, January 17, 2022 at 5:14:30 PM UTC-8 Michael Orlitzky wrote:
>
> > Dark magic is relative, but for someone new [...]
> >
>
> (rant deleted)
>
> 1) "make build" just works
> 2) "./sage -b" just works.
>
It wasn't a rant, th
Wow that is soo awesome. Thanks Tobias!!
On Mon, Jan 17, 2022 at 6:38 PM Matthias Koeppe
wrote:
> On Monday, January 17, 2022 at 5:31:24 PM UTC-8 wst...@gmail.com wrote:
>
>> Unfortunately, the
>> "python setup.py develop" workflow didn't even exist when we first
>> made "sage -b". [...]
On Monday, January 17, 2022 at 5:31:24 PM UTC-8 wst...@gmail.com wrote:
> Unfortunately, the
> "python setup.py develop" workflow didn't even exist when we first
> made "sage -b". [...]
>
It exists now, it is called "pip install --editable" these days.
In the Sage distribution, you activate i
On Monday, January 17, 2022 at 5:14:30 PM UTC-8 Michael Orlitzky wrote:
> Dark magic is relative, but for someone new [...]
>
(rant deleted)
1) "make build" just works
2) "./sage -b" just works.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" grou
On Mon, Jan 17, 2022 at 5:14 PM Michael Orlitzky
wrote:
> On Mon, 2022-01-17 at 17:02 -0800, William Stein wrote:
> >
> >
> > When I wrote this, the steps were:
> >
> > (1) build sage
> > (2) edit the pyx/pxd file you want to change, or really anything in
> > SAGE_ROOT/src/sage
> > (3) type "sage
On Mon, 2022-01-17 at 17:02 -0800, William Stein wrote:
>
>
> When I wrote this, the steps were:
>
> (1) build sage
> (2) edit the pyx/pxd file you want to change, or really anything in
> SAGE_ROOT/src/sage
> (3) type "sage -br" to build any changes and start sage.
>
> Doing "sage -br" should h
On Mon, Jan 17, 2022 at 4:43 PM Michael Orlitzky
wrote:
> On Mon, 2022-01-17 at 15:27 -0800, Randall wrote:
> > I would like to find some developer who is willing to show me how to set
> up
> > the cythonizing part of the compile for the Sage build. I did fix 371
> > warnings in 110 code units, b
On Mon, 2022-01-17 at 15:27 -0800, Randall wrote:
> I would like to find some developer who is willing to show me how to set up
> the cythonizing part of the compile for the Sage build. I did fix 371
> warnings in 110 code units, but have to push these changes back up into the
> cython code.
I
I would like to find some developer who is willing to show me how to set up
the cythonizing part of the compile for the Sage build. I did fix 371
warnings in 110 code units, but have to push these changes back up into the
cython code.
Please contact me if you are willing to give me a few poin
and to fix the remaining doc-cleaning issue, please upgrade again to the
master branch of github (aka tag 3.0.4)
(I would appreciate answers, rather than full silence)
Frédéric
Le vendredi 14 janvier 2022 à 21:25:11 UTC+1, Frédéric Chapoton a écrit :
> also patchbots have persistent problems wi
10 matches
Mail list logo
