If I recall correctly, this is what I did for the FriCAS interface. It
would be nice to factor out any common functionality, if possible.
On Wednesday, 26 April 2023 at 21:06:30 UTC+2 Oscar Benjamin wrote:
> One thing Sage could do with SymPy's RootSum is to call doit which
> will expand using
On Wednesday, April 26, 2023 at 8:40:08 PM UTC-7 William Stein wrote:
On Wed, Apr 26, 2023 at 7:59 PM Matthias Koeppe
wrote:
Just as a data point, eliminating the spkg and only supporting system PARI
2.15.x would have the effect to eliminate support of:
- all versions of Ubuntu except for
On Wed, Apr 26, 2023 at 7:59 PM Matthias Koeppe
wrote:
> On Wednesday, April 26, 2023 at 7:37:17 PM UTC-7 Michael Orlitzky wrote:
>
> On 2023-04-26 18:38:32, Matthias Koeppe wrote:
> > Michael, do you happen to have a suggestion what version range of PARI
> the
> > Sage library should be
On Wednesday, April 26, 2023 at 7:37:17 PM UTC-7 Michael Orlitzky wrote:
On 2023-04-26 18:38:32, Matthias Koeppe wrote:
> Michael, do you happen to have a suggestion what version range of PARI
the
> Sage library should be supporting?
PARI doesn't strictly follow semver, so whatever I say
On 2023-04-26 18:38:32, Matthias Koeppe wrote:
> Michael, do you happen to have a suggestion what version range of PARI the
> Sage library should be supporting?
PARI doesn't strictly follow semver, so whatever I say here, PARI will
eventually make a fool of me. Still, I think a fair goal is to
Michael, do you happen to have a suggestion what version range of PARI the
Sage library should be supporting?
On Wednesday, April 26, 2023 at 4:18:29 PM UTC-7 Michael Orlitzky wrote:
> On Wed, 2023-04-26 at 13:06 -0700, Matthias Koeppe wrote:
> >
> > 2. I'm not in favor of chipping away 1
I've reposted this last message in a separate thread.
On Wednesday, April 26, 2023 at 5:05:56 PM UTC-7 Matthias Koeppe wrote:
> Thanks, John. But I think it's more productive to ask:
> **What was/is/will be the *purpose* of maintaining the Sage distribution?**
> (Historically; as of today; and
A previous sage-devel thread led to this question, which I think is
important and timely to discuss.
**What was/is/will be the *purpose* of maintaining the Sage distribution?**
(Historically; as of today; and looking forward by a year or two.)
Here are some of my thoughts on this question:
1.
Thanks, John. But I think it's more productive to ask:
**What was/is/will be the *purpose* of maintaining the Sage distribution?**
(Historically; as of today; and looking forward by a year or two.)
Here are some of my thoughts on this question:
1. Ease of installation.
Historically, an
On Wed, 2023-04-26 at 13:06 -0700, Matthias Koeppe wrote:
>
> 2. I'm not in favor of chipping away 1 package at a time in the name
> of unsubstantiated, vague notions that a package is "ballast slowing
> down Sage's progress".
>
There's a ticket open to update PARI within Sage. First, upstream
In an attempt to make this less of a religious war and more akin to
something like a rational discussion:
- The status quo is that we include Python3 and gcc. If you want to argue
for their removal, you need to provide evidence that this will not cause
problems for people on supported
On Wednesday, April 26, 2023 at 1:46:41 PM UTC-7 Dima Pasechnik wrote:
On Wed, Apr 26, 2023 at 9:06 PM Matthias Koeppe
wrote:
> 2. I'm not in favor of chipping away 1 package at a time in the name of
unsubstantiated, vague notions that a package is "ballast slowing down
Sage's progress".
On Wednesday, April 26, 2023 at 1:46:41 PM UTC-7 Dima Pasechnik wrote:
we can barely keep up with security updates for e.g. openssl. It
took Thierry to provide a patch today, and me converting it into a PR,
else we probably would be still shipping openssl version with severe
CVEs.
You know
On Wednesday, April 26, 2023 at 1:46:41 PM UTC-7 Dima Pasechnik wrote:
On Wed, Apr 26, 2023 at 9:06 PM Matthias Koeppe
wrote:
> My 2023 summary of the situation:
>
> 1. I would be in favor of abandoning the Sage distribution (despite the
fact that I have certainly put a lot of time and
On Wed, Apr 26, 2023 at 9:06 PM Matthias Koeppe
wrote:
>
> On Wednesday, April 26, 2023 at 12:33:13 PM UTC-7 William Stein wrote:
>
> On Wed, Apr 26, 2023 at 12:27 PM David Roe wrote:
> > I do think it would be valuable for other people on this list to offer some
> > thoughts on whether Sage
Dima,
The word "G..v..d...e" is the worst curse in the Dutch language. The first
three letters needs no translation. The rest translates to 'damn'. You
shouldn't use it lightly.
Jaap
Op wo 26 apr. 2023 21:20 schreef Dima Pasechnik :
> On Wed, Apr 26, 2023 at 8:18 PM Matthias Koeppe
> wrote:
>
On Wednesday, April 26, 2023 at 12:33:13 PM UTC-7 William Stein wrote:
On Wed, Apr 26, 2023 at 12:27 PM David Roe wrote:
> I do think it would be valuable for other people on this list to offer
some thoughts on whether Sage should prioritize reducing the number of
foundational packages we
On Wed, Apr 26, 2023 at 12:27 PM David Roe wrote:
>
> I'm sorry to have prompted another flame war, but please keep the tone polite
> Dima and Matthias. I know that you're both frustrated at this issue being
> unresolved, but it's not appropriate to have a fight like this that goes to
> 2570
I'm sorry to have prompted another flame war, but please keep the tone
polite Dima and Matthias. I know that you're both frustrated at this issue
being unresolved, but it's not appropriate to have a fight like this that
goes to 2570 different people's inboxes, with frequent emails sniping at
each
Hi Everybody,
Just a reminder of
https://github.com/sagemath/sage/blob/develop/CODE_OF_CONDUCT.md
In particular,
1. Be friendly and patient.
2. Be welcoming.
3. Be considerate.
4. Be respectful and polite.
As a community, we've agreed that these are very reasonable ways to
conduct ourselves on
On Wed, Apr 26, 2023 at 8:18 PM Matthias Koeppe
wrote:
>
> On Wednesday, April 26, 2023 at 12:14:26 PM UTC-7 Dima Pasechnik wrote:
>
> This discussion happened 2 years ago
>
>
> That's correct, and you have not brought forward any new points.
Godverdomme, this was about GFORTRAN!!!
WE ARE
On Wednesday, April 26, 2023 at 12:14:26 PM UTC-7 Dima Pasechnik wrote:
This discussion happened 2 years ago
That's correct, and you have not brought forward any new points.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
And Mattias, ffs, we are talking about removing *Python*, and you cite a
thread on removing *gfortran*. This is a very bad way of conducting a
discussion, and it is not the 1st time you do this sort of thing. Please
stop.
On Wed, 26 Apr 2023, 20:10 Matthias Koeppe,
wrote:
> On Wednesday, April
This is ludicrous. This discussion happened 2 years ago, and I really think
if anyone needs a hand-built Python, they can please themselves with
building it. But on macOS in particular the Python supplied by python.org
has been doing fine, for years.
On Wed, 26 Apr 2023, 20:10 Matthias Koeppe,
On Wednesday, April 26, 2023 at 10:40:27 AM UTC-7 Dima Pasechnik wrote:
We should remove python3 spkg, and gcc spkg too, for the same reason.
It's a ballast slowing down Sage's progress.
This is an unsubstantiated claim that you keep repeating.
The last substantial discussion of this proposal
On Wed, 26 Apr 2023, 20:03 Matthias Koeppe,
wrote:
> On Wednesday, April 26, 2023 at 10:25:37 AM UTC-7 David Roe wrote:
>
> On Wed, Apr 26, 2023 at 6:41 AM Dima Pasechnik wrote:
>
> PS. I think openssl spkg should just be removed from Sage, it serves
> no purpose as far as I can tell.
>
>
> For
Here is list of integrals that fail in sagemath from this one file. It
seems Piecewise and RootSum are the cause of these failures.
sagemath version
var('A B a alpha b beta m n x ')
integrate(x/((b*x^2+a)^m),x, algorithm="sympy")
integrate(1/(b*x^3+a),x, algorithm="sympy")
One thing Sage could do with SymPy's RootSum is to call doit which
will expand using radical formulae if possible:
x**2/(3*a**2 + 3*a*b*x**3) + RootSum(729*_t**3*a**4*b**2 + 1,
Lambda(_t, _t*log(81*_t**2*a**3*b + x)))
In [37]: x, a, b, _t = symbols('x, a, b, _t')
In [38]: expr = x**2/(3*a**2 +
On Wednesday, April 26, 2023 at 10:25:37 AM UTC-7 David Roe wrote:
On Wed, Apr 26, 2023 at 6:41 AM Dima Pasechnik wrote:
PS. I think openssl spkg should just be removed from Sage, it serves
no purpose as far as I can tell.
For a long time it was very important for getting a functional Sage on
looks like Piecewise () is another non-implemented conversion - although
it's probably easy to fix.
On Wed, 26 Apr 2023, 19:55 'Nasser M. Abbasi' via sage-devel, <
sage-devel@googlegroups.com> wrote:
> Not all failed one is due to RootSum. Here is one that fails in sagemage
> but works in sympy
Not all failed one is due to RootSum. Here is one that fails in sagemage
but works in sympy and does not generate RootSum but Piecewise
var('A B a alpha b beta m n x ')
integrate(x^(1/2)/(b*x+a),x, algorithm="sympy")
---
Thanks for showing this. As far as I know, the problem is that Sage does
not support RootSum expressions - although they are very useful for
integration in particular.
On Wed, 26 Apr 2023, 19:22 'Nasser M. Abbasi' via sage-devel, <
sage-devel@googlegroups.com> wrote:
> I use sagemath to run the
I use sagemath to run the independent CAS integrations tests for Fricas,
Giac and Maxima, since it is much easier to use the same script to all CAS
systems instead of learning how to use each separate CAS. The result is put
on this page
On Wed, Apr 26, 2023 at 10:40 AM Dima Pasechnik wrote:
> > For a long time it was very important for getting a functional Sage on
> > MacOS; is that no longer the case?
> Sorry, I don't understand.
>
> Noone I know builds Python (the only package that needs openssl) from source.
> For a long
On Wed, Apr 26, 2023 at 6:25 PM David Roe wrote:
>
>
>
> On Wed, Apr 26, 2023 at 6:41 AM Dima Pasechnik wrote:
>>
>> PS. I think openssl spkg should just be removed from Sage, it serves
>> no purpose as far as I can tell.
>
>
> For a long time it was very important for getting a functional Sage
On Wed, Apr 26, 2023 at 6:41 AM Dima Pasechnik wrote:
> PS. I think openssl spkg should just be removed from Sage, it serves
> no purpose as far as I can tell.
>
For a long time it was very important for getting a functional Sage on
MacOS; is that no longer the case?
David
>
> On Wed, Apr 26,
I put a few remarks related to this in a notebook:
https://cocalc.com/wstein/support/SR-and-strings
Basically, converting to from strings via str hardly works anywhere in
Sage and that is by design, following the lead of Magma instead of
Pari. Instead Pickle is the thing that mostly works for
While
sage_eval('sin(x)')
does not work,
sage_eval('sin(x)', {'x': x})
does work. sage_eval needs to know the context (which variables have been
defined, etc.) in which to evaluate. I am not an expert, but
sage_eval('sin(x)', locals=locals())
might work pretty reliably, without
I have opened https://github.com/sagemath/sage/issues/35572 to deal with this
On Wed, Apr 26, 2023 at 10:27 AM dimpase wrote:
>
> On Tue, Apr 25, 2023 at 11:08:02PM -0700, 'Nasser M. Abbasi' via sage-devel
> wrote:
> > I read integrals from a file. They all are stored as strings.
> >
> > Then
PS. I think openssl spkg should just be removed from Sage, it serves
no purpose as far as I can tell.
On Wed, Apr 26, 2023 at 10:32 AM Thierry
wrote:
>
> Hi,
>
> Sage's current openssl version (3.0.5) hass several "High severity"
> vulnerabilities, see
Thanks, it's now https://github.com/sagemath/sage/pull/35571
On Wed, Apr 26, 2023 at 10:32 AM Thierry
wrote:
>
> Hi,
>
> Sage's current openssl version (3.0.5) hass several "High severity"
> vulnerabilities, see https://www.openssl.org/news/vulnerabilities.html
>
> It would be nice to have the
Hi,
Sage's current openssl version (3.0.5) hass several "High severity"
vulnerabilities, see https://www.openssl.org/news/vulnerabilities.html
It would be nice to have the fixes included in the next Sage release. I am not
using github, here is a pull request (literally) to fix this :
git pull
On Tue, Apr 25, 2023 at 11:08:02PM -0700, 'Nasser M. Abbasi' via sage-devel
wrote:
> I read integrals from a file. They all are stored as strings.
>
> Then use SR('expression') inside sagemath to convert them to sagemath
> symbolic expression before calling integrate.
>
> Some give parsing
I can't use SR(sage_eval(' expression')) Now all my integral are failing.
Here is an example
>sage
│ SageMath version 9.8, Release Date: 2023-02-11 │
│ Using Python 3.11.1. Type "help()" for help. │
sage: var('x')
x
sage: SR(sage_eval('sin(x)'))
I think the problem is that the SR exression parses does not know about
python's "(a,b)" tuple notation. If you replace the round brackets with
square brackets, it does seem to work; at least for the example you give:
sage: SR('hypergeometric([3/2,], [5/2, 3], -1/4*3^2)')
I read integrals from a file. They all are stored as strings.
Then use SR('expression') inside sagemath to convert them to sagemath
symbolic expression before calling integrate.
Some give parsing error.
Is using SR('expression') not the correct way to convert string to a
symbolic
46 matches
Mail list logo
