Re: [sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Vincent Delecroix
Le 04/02/2020 à 15:44, Isuru Fernando a écrit : How is making this standard affect the plans for making sage pip installable? This would be the first package in a while that depends on sage-the-library that is also standard in sage-the-distribution. That is a good point which emphasizes the fa

Re: [sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Isuru Fernando
How is making this standard affect the plans for making sage pip installable? This would be the first package in a while that depends on sage-the-library that is also standard in sage-the-distribution. Isuru -- You received this message because you are subscribed to the Google Groups "sage-dev

[sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Nathan Dunfield
On Monday, February 3, 2020 at 4:52:44 PM UTC-6, Samuel Lelievre wrote: > > Please vote for making giacpy_sage a standard package. > +1 The "giacpy_sage" optional package is one I always install when I build Sage and it has been robust in my experience. As others have said, given that giac its

Re: [sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread mmarco
You mean having a function (or global variable) to set which will be the default backend? I find that having a workflow consisting on expressions like: integrate(foo,x,algorithm='giac') is not specially comfortable, but even then, I prefear it to something like: set_integration_backend('giac')

Re: [sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Dima Pasechnik
On Tue, Feb 4, 2020 at 9:46 AM mmarco wrote: > > +1 > > Also, I suggest that we consider the possibility of using giac as the default > backend for symbolic integration. I guess we need to develop a setup to switch from one default integration backend to another. > > > El lunes, 3 de febrero de

[sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread mmarco
+1 Also, I suggest that we consider the possibility of using giac as the default backend for symbolic integration. El lunes, 3 de febrero de 2020, 23:52:44 (UTC+1), Samuel Lelievre escribió: > > Please vote for making giacpy_sage a standard package. See > > - Sage Trac ticket: 28918 > Make g

[sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Simon King
On 2020-02-04, Markus Wageringel wrote: > Giacpy_sage provides C-bindings for Giac which is already a standard > package. So making Giacpy_sage a standard package as well would allow to > replace pexpect calls to Giac by C-calls, which is the overarching goal of > #16688. Giac is currently used

Re: [sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Dima Pasechnik
+1 from me too. On Tue, Feb 4, 2020 at 8:27 AM Markus Wageringel wrote: > > Giacpy_sage provides C-bindings for Giac which is already a standard package. > So making Giacpy_sage a standard package as well would allow to replace > pexpect calls to Giac by C-calls, which is the overarching goal o

[sage-devel] Re: Poll: make giacpy_sage a standard package

2020-02-04 Thread Markus Wageringel
Giacpy_sage provides C-bindings for Giac which is already a standard package. So making Giacpy_sage a standard package as well would allow to replace pexpect calls to Giac by C-calls, which is the overarching goal of #16688. Giac is currently used as fallback for symbolic integration where this