I was about to open a new issue for work I have done which will implement a
greatly improved method for something already implemented in Sage (twice,
both by me...). When you click on the button to create a new issue, there
are three categories listed: Bug Report, Failure Building from Source, and
if you already have the code, a PR would do, no need for an issue, IMHO.
On Thu, Feb 16, 2023 at 9:04 AM John Cremona wrote:
>
> I was about to open a new issue for work I have done which will implement a
> greatly improved method for something already implemented in Sage (twice,
> both by me..
Hello;
Are there any plans to add support to calling/using REDUCE from inside
Sagemath as one can now do with other CAS systems such as
maxima/giac/fricas etc..
https://reduce-algebra.sourceforge.io/
--Nasser
--
You received this message because you are subscribed to the Google Groups
"sage
On Thu, 16 Feb 2023 at 10:18, Dima Pasechnik wrote:
> if you already have the code, a PR would do, no need for an issue, IMHO.
>
Good point. But between some stand-alone code and properly integrating the
functionality into Sage takes time and effort (which I am now in the middle
of), and I migh
Deprecation warnings have a parameter which is interpreted as a trac ticket
number, and output a second line after the warning text, of the form
See https://trac.sagemath.org/12345 for details.
Is the solution simply to replace the template for that output with a
suitable GitHub issue number (or
On Thu, 16 Feb 2023 at 15:53, John Cremona wrote:
> Deprecation warnings have a parameter which is interpreted as a trac
> ticket number, and output a second line after the warning text, of the form
>
> See https://trac.sagemath.org/12345 for details.
>
> Is the solution simply to replace the tem
this has been taken care of in PR 35015
On Thu, 16 Feb 2023, 15:54 John Cremona, wrote:
>
>
> On Thu, 16 Feb 2023 at 15:53, John Cremona wrote:
>
>> Deprecation warnings have a parameter which is interpreted as a trac
>> ticket number, and output a second line after the warning text, of the for
On Thu, 16 Feb 2023, 16:59 Dima Pasechnik, wrote:
> this has been taken care of in PR 35015
>
Thanks, I should have guessed that this had already been dealt with.
There are a lot of PRs with positive review (maybe there always were). Has
the release manager's job become harder? I assume that
On Thu, 16 Feb 2023, 17:33 John Cremona, wrote:
>
>
> On Thu, 16 Feb 2023, 16:59 Dima Pasechnik, wrote:
>
>> this has been taken care of in PR 35015
>>
>
>
> Thanks, I should have guessed that this had already been dealt with.
>
> There are a lot of PRs with positive review (maybe there always w
I'm pretty sure there are no such plans, but it would be entirely possible
to write such an interface. This can be done with no overhead as an
external package first (just a python module that is dependent on the
sagemath library). Once it exists, its popularity may indicate if it's
worth incor
Hi,
You may use
https://github.com/sagemath/sage/wiki
as a portal to interesting issues/prs.
--
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
>From "PowerSeriesRing" docstring:
There is a unique power series ring over each base ring with given
variable name. Two power series over the same base ring with
different variable names are not equal or isomorphic.
However (and I think it should be like that):
sage: P1.=PowerSeriesRin
On Fri, Feb 17, 2023 at 6:04 AM Nils Bruin wrote:
> From "PowerSeriesRing" docstring:
>
>There is a unique power series ring over each base ring with given
>variable name. Two power series over the same base ring with
>different variable names are not equal or isomorphic.
>
> However
13 matches
Mail list logo
