Re: [sage-devel] On backdooring open source projects

I’d like to point out that Sage, by it’s very nature, *is* a large bundle of other people’s packages, offering them a (more or less) unified interface, thus ensuring interoperability. To reuse a simile used in Sage’s initial statements of intent, Sage is a car using many already- pepared

[sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

Le mercredi 28 février 2024 à 17:39:25 UTC+1, Eric Gourgoulhon a écrit : -1 from my side, for I think an issue can be a blocker. For instance: https://github.com/sagemath/sage/issues/36914 This issue, which regards the use of the notebook, could not have been detected by the CI framework. It

Re: [sage-devel] Re: Unload "blocker" label

Le lundi 26 février 2024 à 12:59:47 UTC+1, Dima Pasechnik a écrit : On Mon, Feb 26, 2024 at 11:36 AM Kwankyu Lee wrote: On Monday, February 26, 2024 at 6:49:35 PM UTC+9 Dima Pasechnik wrote: >usage 3: Issues that should be fixed as fast as possible > >To me it is rather "issues that should

Re: [sage-devel] Re: Unload "blocker" label

Le lundi 26 février 2024 à 12:59:47 UTC+1, Dima Pasechnik a écrit : [ Snip... ] Are you saying that only PRs can block a release? But how does one even report a very serious issue, without offering a ready fix? Are you saying one should use other channels of communication for this?

[sage-devel] Re: Exception in sum((4*n+1)/factorial(n),n,1,oo)

Le vendredi 9 février 2024 à 15:42:30 UTC+1, Eric Gourgoulhon a écrit : I confirm the bug with Sage 10.3.beta7. It seems to be linked with the Maxima interface. Meanwhile, a workaround is to use the SymPy interface: sage: sum((4*n+1)/factorial(n), n, 1, oo, algorithm='sympy') 5*e - 1 FWIW,

[sage-devel] Re: Wanted: Unicode testers with PR #36861

I seond the previous arguments for switching to lualatex rather than xetex : the former is *officially* the heir apparent to pdftex, while the latter is bound to become an historical, then unmaintained, then paleontological piece of software… And, yes, supporting Unicode is a necessity.

Re: [sage-devel] Poll: deprecate backslash operator

BTW :the changes and advances made in Sage since the last edition of this book may warrant a revision, possibly a new edition. If only for the installation procedures (Conda installation, WSL on Windows, Github replacing Trac, etc...) and the interfaces (Jupyter replacing the Sage notebook,

[sage-devel] Re: strange error from integrate command with maxima 5.47 and sagemath 10.1 beta 6

Le lundi 17 juillet 2023 à 04:59:53 UTC+2, Nasser M. Abbasi a écrit : fyi, added PR https://github.com/sagemath/sage/issues/35960 Would you conider posting your *upgrade* to Maxima (5.46.0 to 5.47.0) as a PR ? On Sunday, July 16, 2023 at 12:30:53 PM UTC-5 Matthias Koeppe wrote: On Sunday,

Re: [sage-devel] Re: How to use maxima 5.47 with sagemath 10.1 beta?

Le dimanche 16 juillet 2023 à 13:14:14 UTC+2, Dima Pasechnik a écrit : [ Snip... ] Some flavours of Linux, e.g. Gentoo (and Debian?) allows you to have maxima built with ECL system+wide. Not Debian, alas... unless you bite the bullet and install the whole "*sage*" packaging of Sage ...

[sage-devel] Re: strange error from integrate command with maxima 5.47 and sagemath 10.1 beta 6

FWIW, neither Maxima, Giac, Sympy, Fricas, the Wolfram engine nor the Rubi integrator seem to be able to give a closed form to this antiderivative… - Maxima (5.46.0) fails as reported above relatively quickly (a few seconds). - the default integrator (i. e. what is called

Re: [sage-devel] Re: ECL says: Memory limit reached calling expr.full_simplify()

Similarly : sage: expr.expand() 0 sage: expr.factor() 0 HTH, ​ Le samedi 24 juin 2023 à 09:40:16 UTC+2, Emmanuel Charpentier a écrit : > FWIW : > sage: reset() sage: > expr=(1-x)^3+(-x^2+x)^3+(x^2-1)^3-3*(1-x)*(-x^2+x)*(x^2-1) sage: > expr.is_zero() True > >

Re: [sage-devel] Re: ECL says: Memory limit reached calling expr.full_simplify()

FWIW : sage: reset() sage: expr=(1-x)^3+(-x^2+x)^3+(x^2-1)^3-3*(1-x)*(-x^2+x)*(x^2-1) sage: expr.is_zero() True full_simplify may not be necessary… HTH, ​ Le samedi 24 juin 2023 à 06:38:35 UTC+2, Nasser M. Abbasi a écrit : > " yes, simplification (particularly full simplification) can

Re: [sage-devel] Re: ECL says: Memory limit reached calling expr.full_simplify()

FWIW: ``` sage: a, x = var("a, x") sage: Ex0=x/(a^5+x^5) sage: FE1=Ex0.integrate(x, algorithm="fricas") sage: len(repr(FE1)) 47199 ``` Fricas may be out of joint here... FWIW, I have been unable to typeset this expression with neither `pdflate` nor `xelatex`. The only way I had to visualize it

[sage-devel] A patch request on `sage-cell-mode` is awaiting maintainer's intervention.

This patch request on sage-cell-mode has been ready for review for about a month. Could some kind-souled maintainer give it a look ? Thnks in advance ! ​ -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

I'd like to stress one important point already made : dropping support for old/antique/paleontologic versions of Python lightens the maintainance workload of the *small* team of Sage developpers. Given the size and the state of this team, this point should *not* be taken lightly... I'd also

Re: [sage-devel] Re: Problematic SR interpretation of radicals (and non-integer rational exponents) in Sage.

gt; checks to see which of the solutions satisfy the original radical > equations. Passing check=False means that the checking is disabled and so > you get all solutions to the polynomial equation which may or may not be > solutions to the radical equation. > > -- > Oscar >

[sage-devel] Re: Problematic SR interpretation of radicals (and non-integer rational exponents) in Sage.

*Typo* in the preceding message : The polynomial system is of course |x2^2-x1, x3^3-x1, x2+x3+2] Sorry for the noise ! ​ Le samedi 6 mai 2023 à 11:25:07 UTC+2, Emmanuel Charpentier a écrit : > TLDR : Sage easily gets the roots of the polynomial system |x2^2-x1, > x3^4-x1, x

[sage-devel] Problematic SR interpretation of radicals (and non-integer rational exponents) in Sage.

TLDR : Sage easily gets the roots of the polynomial system |x2^2-x1, x3^4-x1, x2+x3+2] but interprets [image: \sqrt[3]{x}+\sqrt{x}+2] inconsistently : this expression is *not* zero for the above roots. Details : see the enclosed Jupyter Lab sheet. This seems to be little discussed in Sage

Re: [sage-devel] web site from cocalc but in our domain

As of Apr 25, 2023 10:24 UTC, this address cant’be found by a browser using .opendns.org nor by linux’s host : charpent@zen-book-flip:/usr/local/sage-10$ host sage.sagemath.org Host sage.sagemath.org not found: 3(NXDOMAIN) Is that the intended result ? HTH, ​ Le mardi 25 avril 2023 à

Re: Re: [sage-devel] ChatGPT is an expert in SageMath too

“Le droit du pauvre est un mot creux” (“Rights of the poor” is a hollow phrase) Eugène Pottier, *L’internationale* (1871). I am somewhat skeptic about the odds of any legal action suceeding against a porential multi-billion $ buisness

Re: [sage-devel] Re: where is rpy2

Ahem... There are two components to consider : - the package by itself - its interface to Sagemath. Case in point : the Mathematica interface, which is standard (*i. e.* installed in all cases), but active if and only if Mathematica (or the Wolfram engine) is present in the target system.

[sage-devel] Re: What happened to Mathematica magics ?

helpful by default), but > fortunately "%" works. It would be great to fix this, too. > > On Wednesday, March 1, 2023 at 12:09:41 AM UTC-8 Emmanuel Charpentier > wrote: > >> Thank you for the explanation. >> >> The short-term fix works, but is noisy. Fur

Re: [sage-devel] Re: Adding labels to github issues

Le dimanche 5 mars 2023 à 14:52:50 UTC+1, Dima Pasechnik a écrit : On Sun, 5 Mar 2023, 13:50 Emmanuel Charpentier, wrote: Dear David, Le mercredi 8 février 2023 à 13:51:40 UTC+1, David Roe a écrit : Yesterday I manually added a bunch of people that I recognized to the sagemath

[sage-devel] Re: Adding labels to github issues

Dear David, Le mercredi 8 février 2023 à 13:51:40 UTC+1, David Roe a écrit : Yesterday I manually added a bunch of people that I recognized to the sagemath organization triage team on github, This currently is 404 (page not found)... which

[sage-devel] Re: What happened to Mathematica magics ?

gic.register_all() > > > On Tuesday, February 28, 2023 at 7:03:24 AM UTC-8 Emmanuel Charpentier > wrote: > >> I don’t use them very often, bu the %mathematica and %%mathematica >> magics seem to have recently disappeared. They don’t appear in the >> %lsmagic out

[sage-devel] What happened to Mathematica magics ?

I don’t use them very often, bu the %mathematica and %%mathematica magics seem to have recently disappeared. They don’t appear in the %lsmagic output, and raise an error when one attempts to use them. Can someone shed any light on this ? ​ -- You received this message because you are

[sage-devel] Re: Migration to GitHub complete

Thank you ! But I already restarted in a fresh tree, which gad the unexpected side effect of seriously deflating its size (9,4 GB vs 24 GB in the old tree...). The migration guide should be amended... Le lundi 6 février 2023 à 16:06:34 UTC+1, Kwankyu Lee a écrit : > Or > > git branch -D

[sage-devel] Re: Migration to GitHub complete

After followong the steps given for an existing tree, my develop branch still followed OLD-ORIGIN. Shouldn't that be orign ? Le lundi 6 février 2023 à 08:02:59 UTC+1, Matthias Koeppe a écrit : > https://github.com/sagemath/sage > > See >

[sage-devel] Re: Doubts about correctness of `integrate(floor(x)^2,x)`

s ``` [image: tmp_7n_jxgco.png] Giac's "antiderivative" implicitly adds `heaviside(x-u)^2` terms... Again, this is wrong... Le vendredi 3 février 2023 à 10:31:17 UTC+1, Emmanuel Charpentier a écrit : > BTW : > > ``` > sage: a, b = var("a, b") > sage: f(x) = floor(x)^2 >

[sage-devel] Re: Doubts about correctness of `integrate(floor(x)^2,x)`

BTW : ``` sage: a, b = var("a, b") sage: f(x) = floor(x)^2 sage: f(x).integrate(x, a, b) // Giac share root-directory:/usr/local/sage-9/local/share/giac/ // Giac share root-directory:/usr/local/sage-9/local/share/giac/ Added 0 synonyms No checks were made for singular points of antiderivative

[sage-devel] Re: Doubts about correctness of `integrate(floor(x)^2,x)`

BTW : sage: a, b = var("a, b") sage: f(x) = floor(x)^2 sage: f(x).integrate(x, a, b) // Giac share root-directory:/usr/local/sage-9/local/share/giac/ // Giac share root-directory:/usr/local/sage-9/local/share/giac/ Added 0 synonyms No checks were made for singular points of antiderivative

[sage-devel] Re: Integral of log() and exp() failing the derivative check

Indeed : ``` sage: f(x)=2^(x-1/2*I*log(-e^(-2*I*pi*x))/pi-1/2) ``` The key is probably ``` sage: f(x).diff(x) 0 ``` This should include an (infinite) series of terms in `dirac(x-k)` for k in integers... Logical consequence : ``` sage: f(x).integrate(x) 1/2*sqrt(2)*(-1)^(-1/2*I*log(2)/pi)*x

[sage-devel] Re: Inverses of matrices over RR

something is *definitely* unhinged here : On 9.8.beta3 running on Debian testing on core i7 + 16 GB RAM, after running : a = RR(-4967757600021511 / 2**106) b = RR(-7769080564883485 / 2**52) c = RR( 5221315298319565 / 2**53) m = matrix([[a, b], [c, -a]]) M = matrix([[var("p%d%d"%(u, v),

[sage-devel] Re: Different results for numerical and symbolic integration

Forgot : I have graphically checked the numerical quasi-equality of the symbolical integral given by Mathematica and the numerical integral given by Sage. Le mardi 25 octobre 2022 à 15:46:13 UTC+2, Emmanuel Charpentier a écrit : > Essentially correct, bit it’s a tad less simpler : > >

[sage-devel] Re: Different results for numerical and symbolic integration

Essentially correct, bit it’s a tad less simpler : sage: f(x) = x^2*(log(x))^4/((x+1)*(1+x^2)) sage: list(map(lambda u:u.integrate(x, 0, 1), f(x).partial_fraction_decomposition())) [-5/128*pi^5 + 45/64*zeta(5), 45/4*zeta(5)] sage: list(map(lambda u:mathematica.Integrate(u, (x, 0, 1)).sage(),

Re: [sage-devel] Solving a system of linear equations with complex numbers yields false solution

FWIW, solve(..., algorithm="sympy") solves this simplified system. HTH, ​ Le jeudi 20 octobre 2022 à 11:16:06 UTC+2, Florian Königstein a écrit : > I'd like to point out that I found a much simpler system of equations for > that it fails. I have also reported in the thread for maxima: >

Re: [sage-devel] Solving a system of linear equations with complex numbers yields false solution

Le lundi 10 octobre 2022 à 20:37:57 UTC+2, Florian Königstein a écrit : I think it would make sense to file a Sage ticket. So when it will be fixed > in Maxima, it can be verified that it (hopefully) will also work in Sage > with the updated version of Maxima. > Done.

Re: [sage-devel] Solving a system of linear equations with complex numbers yields false solution

This problem has been filed in Maxima’s bug report system. Should a Sage ticket be filed ? ​ Le dimanche 9 octobre 2022 à 19:55:07 UTC+2, Florian Königstein a écrit : > Thank you for your efforts. > > Yes, it was me who posted the original post >

Re: [sage-devel] Solving a system of linear equations with complex numbers yields false solution

I posted about the same problem ; the original post in ask.sagemath.org is clearer. The original problem seems

Re: [sage-devel] Solving a system of linear equations with complex numbers yields false solution

I [osted] Le dimanche 9 octobre 2022 à 14:15:57 UTC+2, dim...@gmail.com a écrit : > On Sun, Oct 9, 2022 at 9:23 AM David Joyner wrote: > > > > On Sun, Oct 9, 2022 at 3:25 AM Florian Königstein > wrote: > > > > > > I have equations for the analysis of an electric circuit. They contain > at

[sage-devel] Re: VOTE: move Sage development to Github

+1 for Github Also wishing for contingency plan for re-migrating to self-hosted Gitlab. Le mercredi 21 septembre 2022 à 19:23:36 UTC+2, David Roe a écrit : > Dear Sage developers, > Following extensive discussion, both recently >

Re: [sage-devel] trac.sagemath.org unreachable

to "git trac" >>> >>> On Wed, 31 Aug 2022, 07:45 Emmanuel Charpentier, >>> wrote: >>> >>>> This morning (Aug 31, 2022, 8:43), any attempt to reach ` >>>> trac.sagemath.org` ends up displayong a Python trace : >>>&

[sage-devel] Re: trac.sagemath.org unreachable

it_trac.trac_error.TracInternalError: Of note : I could create a new ticket (the one I was trying to fetch) yesterday afternoon. This might be a problem distinct from the one due to the key change (this week-end, IIUIC). Le mercredi 31 août 2022 à 09:04:43 UTC+2, Emmanuel Charpentier a écrit : >

[sage-devel] Re: trac.sagemath.org unreachable

The Web site is still unreachable. Le mercredi 31 août 2022 à 09:02:53 UTC+2, Emmanuel Charpentier a écrit : > Ditto from Git via SSH : > > ```charpent@zen-book-flip:/usr/local/sage-9$ git fetch > @@@ > @WARNI

[sage-devel] Re: trac.sagemath.org unreachable

changed and you have requested strict checking. Host key verification failed. fatal: Impossible de lire le dépôt distant. Veuillez vérifier que vous avez les droits d'accès et que le dépôt existe. ``` Removing the old SSH key cleared git access. Le mercredi 31 août 2022 à 08:45:29 UTC+2, Emmanuel

[sage-devel] trac.sagemath.org unreachable

This morning (Aug 31, 2022, 8:43), any attempt to reach `trac.sagemath.org` ends up displayong a Python trace : ``` Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/trac/web/api.py", line 602, in send_error data, 'text/html') File

[sage-devel] Re: [sage-support] Sagetex version ?

it to a Python package which uses ninja at build time - and in > fact ninja IS available as Python package. So it is Python enough in my > eyes. > Is ninja already used in building (some part of) Sage ? > On Sat, 20 Aug 2022, 16:06 Emmanuel Charpentier, > wrote: > >&

[sage-devel] Re: Display of scale multiplier in scientific notation (the e notation for powers of ten) is missing for plots starting with 0

Le mercredi 27 juillet 2022 à 16:53:39 UTC+2, niran…@gmail.com a écrit : Dear Kcrisman, > I will look into it *if* you promise me to *review* and *close* my > another ticket https://trac.sagemath.org/ticket/34038 > based on the thread >

[sage-devel] Re: System upgrades breaking sage frequently

FWIW, the very same mishap just happened to me on Debian.testing. What I fail to understand is why Sake was linked to a *specific* version of libflint.so, rather than to the *generic* version… ​ Le mercredi 20 juillet

[sage-devel] Re: latex function and operations with fraction subscripts

The /character cannot be part of a symbol’s name (not acepted by the Python interpreter). Try : sage: logr = SR.symbol("logr", latex_name='L_{x/x_0}') sage: x*logr logr*x sage: latex(x*logr) L_{x/x_0} x BTW (question of taste…), I’d rather use logr = SR.symbol("logr",

[sage-devel] Re: latex function and operations with fraction subscripts

the `/`character cannot be part of a symbol's name (not acepted by the Python interpreter). Try : ``` sage: logr = SR.symbol("logr", latex_name='L_{x/x_0}') sage: x*logr logr*x sage: latex(x*logr) L_{x/x_0} x ``` BTW (question of taste...), I'd rather use `logr = SR.symbol("logr",

[sage-devel] Re: Request for advice : extend exponentialize ?

Never mind : I went ahead and created Trac#34108 <https://trac.sagemath.org/ticket/34108>, which needs_review (hint, hint….). HTH, ​ Le samedi 2 juillet 2022 à 10:32:30 UTC+2, Emmanuel Charpentier a écrit : > The SR.exponentialize method implements : > > sage: [u(x)==u(x)._s

[sage-devel] Re: Request for advice : extend exponentialize ?

Never mind : I went ahead and created [Trac#34108](https://trac.sagemath.org/ticket/34108), which `needs_review` (hint, hint...). HTH, Le samedi 2 juillet 2022 à 10:32:30 UTC+2, Emmanuel Charpentier a écrit : > The SR.exponentialize method implements : > > sage: [u(x)==u(x)._sympy_(

[sage-devel] Re: Request for advice : extend exponentialize ?

t, arcsinh, arccosh, arctanh, arccsch, arcsech, arccoth))) True ​ Le samedi 2 juillet 2022 à 10:32:30 UTC+2, Emmanuel Charpentier a écrit : > The SR.exponentialize method implements : > > sage: [u(x)==u(x)._sympy_().rewrite("exp")._sage_() > : for u in (sin, cos, tan,

[sage-devel] Request for advice : extend exponentialize ?

The SR.exponentialize method implements : sage: [u(x)==u(x)._sympy_().rewrite("exp")._sage_() : for u in (sin, cos, tan, csc, sec, cot, sinh, cosh, tanh, csch, sech, coth)] [sin(x) == -1/2*I*e^(I*x) + 1/2*I*e^(-I*x), cos(x) == 1/2*e^(I*x) + 1/2*e^(-I*x), tan(x) == -I*(e^(I*x) -

Re: [sage-devel] Can't push to trac...

Le dimanche 26 juin 2022 à 22:58:07 UTC+2, dim...@gmail.com a écrit : > > > On Sun, 26 Jun 2022, 21:54 Emmanuel Charpentier, > wrote: > >> Nope : >> >> charpent@zen-book-flip:/usr/local/sage-9$

Re: [sage-devel] Can't push to trac...

: > > > On Sun, 26 Jun 2022, 21:07 Emmanuel Charpentier, > wrote: > >> I recently created [Trac#34087](https://trac.sagemath.org/ticket/34087) >> and created a commit fixing a (minor) problem of (back)translations to >> Mathematica. But I'm unable

[sage-devel] Can't push to trac...

I recently created [Trac#34087](https://trac.sagemath.org/ticket/34087) and created a commit fixing a (minor) problem of (back)translations to Mathematica. But I'm unable to push the coimmit. First atempt : ``` charpent@zen-book-flip:/usr/local/sage-9$ git trac push Pushing to Trac #34087...

[sage-devel] Re: Possible bug in the symbolic differentiation of N unknown variables

As I understand it, differentiating a *discrete* sum with respect to its bounds is nonsense ; see my comment in the ticket. ​ Le samedi 28 mai 2022 à 09:02:53 UTC+2, Nils Bruin a écrit : > Actually, this case is fully covered by > > https://trac.sagemath.org/ticket/32161 > > which is,

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

On a seemingly unrelated note which is actually quite related, I don’t think it would be possible to find this out, but it would be interesting to know at what rate there has been user -> developer conversion over the years. Depends on the definition of conversion. In olden times, you might

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

Neither approach assumes anything, but using “make” is at least familiar to anyone who has built any unix software in the past 30 years This is a null measure set of Windows users (and probably of Mac users). Especially of undergrad students, which are (or should be) a very sizable portion

[sage-devel] Re: Error building sage r-3.6.3 (Ubuntu 18.04)

Well… - config can’t detect readline, and configures Sage to install the relevant SPKG. - Compilation of r fails for lack of readline. Did you check the compilation of the readline SPKG ? (You should have something matching *readline*.log somewhere under

[sage-devel] Re: Looks like a problem somewhere!

WorksForMe(TM) in 9.6.rc0 : sage: d = {0: [2,3,5], 1: [3,4,5], 2: [4],3:[5]}; sage: H=Graph(d) sage: H.is_line_graph() False HTH, ​ Le lundi 18 avril 2022 à 22:41:31 UTC+2, hany.mha...@gmail.com a écrit : > Guys, > I was playing with sage executing this code: > d = {0: [2,3,5], 1: [3,4,5], 2:

[sage-devel] Re: Something.expand() is 0 but factor() is not zero

sage: var("x, y, z") (x, y, z) sage: Ex = (x-y)^2*(y-z)*(z-x) + (y-z)^2*(z-x)*(x-y) + (z-x)^2*(x-y)*(y-z) sage: Ex -(x - y)^2*(x - z)*(y - z) + (x - y)*(x - z)^2*(y - z) - (x - y)*(x - z)*(y - z)^2 sage: Ex.expand() 0 sage: Ex.factor() -(x - y)^2*(x - z)*(y - z) + (x - y)*(x - z)^2*(y - z) - (x

[sage-devel] Re: %lsmagic broken in sage interpreter

That's Trac#30661 ... HTH, Le dimanche 13 mars 2022 à 18:14:48 UTC+1, Eric Gourgoulhon a écrit : > This is https://trac.sagemath.org/ticket/30661 > > A workaround is > sage: %display unicode_art# actually anything but plain > sage: %lsmagic > > Eric.

[sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.6

I just checked that my (systemwide) sympy is 1.10, and that Sage’s sympy is still 1.9… ​ Le vendredi 11 mars 2022 à 13:11:48 UTC+1, Emmanuel Charpentier a écrit : > As of 9.6.beta4, sympy is still version

[sage-devel] Re: https://wiki.sagemath.org/ReleaseTours/sage-9.6

As of 9.6.beta4, sympy is still version 1.9 : ┌┐ │ SageMath version 9.6.beta4, Release Date: 2022-03-08 │ │ Using Python 3.9.10. Type "help()" for help. │

Re: [sage-devel] I have lost access to g...@git.sagemath.org:sage.git

keys get rejected by newer versions of sshd. > > A id_ed25519 key type appears to be a good choice. > > Dima > > > > On Sat, 19 Feb 2022, 12:51 Emmanuel Charpentier, > wrote: > >> An attempt at a routine git fetch (on the machine I have used for > 2 >> y

[sage-devel] I have lost access to g...@git.sagemath.org:sage.git

An attempt at a routine git fetch (on the machine I have used for > 2 years…) fails : charpent@zen-book-flip:/usr/local/sage-9$ git fetch g...@git.sagemath.org: Permission denied (publickey). fatal: Impossible de lire le dépôt distant. Veuillez vérifier que vous avez les droits d'accès et que

[sage-devel] Re: Bug with a very specific integral computed with giac

raeve, Institut Fourier, Universite de Grenoble I" But now, ptestlong exhibits new bugs <https://groups.google.com/g/sage-release/c/aOpjpfOXgro/m/03WJYuNTFwAJ>. Sigh (again)… HTH, ​ Le dimanche 30 janvier 2022 à 07:25:48 UTC+1, Emmanuel Charpentier a écrit : > To add insult to injury,

[sage-devel] Re: Bug with a very specific integral computed with giac

Le dimanche 30 janvier 2022 à 10:48:27 UTC+1, Samuel Lelievre a écrit : > 2022-01-30 05:10:25 UTC, Emmanuel Charpentier: > > > > After upgrading to 9.5.rc5 and disabling system’s pari and singular > > Did you mean "after upgrading to 9.5.rc4"? > Yes, of course.

[sage-devel] Re: Bug with a very specific integral computed with giac

To add insult to injury, trying to re-enable system’s giac (make giac-clean && configure failed. Somehow,./configurefinds no *suitable* systemgiacversion, and re-builds Sage's giac. It seems that I should also cleanpari` and consorts and re-re-build… Sigh… ​ Le vendredi 28 janvier 2022 à

[sage-devel] Re: Bug with a very specific integral computed with giac

Okay. That’s a nice one… After upgrading to 9.5.rc5 *and disabling system’s pari and singular* (for other reasons, see there ), configure somehow decided to install the giac SPKG and not to use system’s giac. This triggered the

Re: [sage-devel] Re: 32768

Le mercredi 19 janvier 2022 à 14:44:29 UTC+1, kcrisman a écrit : > In addition, for me its a matter of sustainability to use things as long >> as they work. > > > +1 > +1. And important in more ways than mathematical... -- You received this message because you are subscribed to the Google

[sage-devel] Re: Bug with a very specific integral computed with giac

Can’t reproduce on Sage 9.5.rc1 running in Debian testing. First thing after session start : sage: integrate(e^x/(x^2+1), x, -pi, pi) // Giac share root-directory:/usr/share/giac/ // Giac share root-directory:/usr/share/giac/ Added 0 synonyms 1/2*(imag_part(Ei(pi + I))*tan(1/2)^2 -

[sage-devel] Re: Proposal: Stop providing binary distributions

Mixed feelings... See my comments on the ticket. Le samedi 8 janvier 2022 à 20:10:15 UTC+1, Matthias Koeppe a écrit : > Comments/review please in https://trac.sagemath.org/ticket/33131 > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] ask.sagemath.org down ?

About Dec 28, 2021 15:00 CET ask.sagemath.org doesn't answer. ISTR that it runs on some computer at Université Paris Sud. Can someone check me on this ? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Re: ask.sagemath.org issues - do we need it?

Discourse is somewhat nosy : I have to use it for questions related to Stan ... Le samedi 11 décembre 2021 à 18:52:34 UTC+1, Matthias Koeppe a écrit : > On Saturday, December 11, 2021 at 7:00:54 AM UTC-8 kcrisman wrote: > >> As for sage-support, it's always surprising to

[sage-devel] Re: A simple funny bug in Sagemath

WorksForMe(TM) in 9.5.beta7. Le mardi 7 décembre 2021 à 10:54:48 UTC+1, Eric Gourgoulhon a écrit : > Hi, > > It works for me with SageMath 9.4. Maybe you should upgrade to that > version (the last stable one). > > Eric. > > Le mardi 7 décembre 2021 à 09:59:42 UTC+1, duan...@gmail.com a écrit

[sage-devel] Re: Demote SageTeX to an optional package?

Having a *standard* way to integrate Sage’s results in a document is **crucial*. So -1. Counter-proposal : add a pseudo-package à la tinytex (which tests for a local TeX installation, and install a minimal TeX if necessary).

[sage-devel] Re: making primecount (and its dependency primesieve) standard

+1, of course... Le mardi 23 novembre 2021 à 11:26:44 UTC+1, dim...@gmail.com a écrit : > primecount is a popular C++ library of efficient procedures to > compute prime_pi(x), i.e. π(x), > number of prime numbers <=x, and related functions. > It's an optional package now. The repo is >

Re: [sage-devel] Refactoring/modularization work on the Symbolic Ring

Le jeudi 26 août 2021 à 13:25:50 UTC+2, kcrisman a écrit : >> E.g. it looks like integration is not there. >> > > If I recall correctly, we use ginac/pynac only for symbolics proper (i.e. > not calculus), as well as for differentiation. I don't know if symengine > is something to switch

[sage-devel] A patchbot error I do not understand

I am working on Trac#10038 , and, so far, two patchbots fail to build (for lack of pynac-config.h) and two other build successfully but fail one doctest : * File

[sage-devel] A ticket that may need special attention :

This ticket , result from this ask.sagemath question , may be worth some special attention : it shows a way for Sage to grab all available memory, and

[sage-devel] Re: symbolic rootof object

You may work on the univariate polynamial ring in your variable of interest over a suitable ring. A simple example : sage: var("x, y, z") (x, y, z) sage: foo=x^3-x*sin(y+z)+1 sage: foo.polynomial(ring=PolynomialRing(SR,"x")).parent() Univariate Polynomial Ring in x over Symbolic Ring sage:

[sage-devel] ask.sagemath.org down ?

I could connect to ask.sagemath.org on Jul 8, 2021 at about 7:30 CEST, but no longer around 8;30 CEST. Air conditioning acting up again ? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] Re: missing '^' logical operator : bug (oversight) or design ?

Thank you very much ! I didn't know that. I note that this information is a bit difficult to reach in the documentation... and tha, in my Sage installation (from git tree, on Debian testing), "search_doc" is broken. Le dimanche 16 mai 2021 à 09:51:39 UTC+2, Nils Bruin a écrit : > If the

[sage-devel] missing '^' logical operator : bug (oversight) or design ?

Dear list, consider python : >>> a = set(['a', 'b', 'c']) >>> b = set(['b', 'c', 'd']) >>> a & b {'b', 'c'} >>> a | b {'b', 'a', 'd', 'c'} >>> a - b {'a'} >>> a ^ b {'a', 'd'} vs Sage : sage: a = set(['a', 'b', 'c']) sage: b = set(['b', 'c', 'd']) sage: a & b {'b', 'c'} sage: a | b {'a',

[sage-devel] Re: Preliminary bug [Re: Boolean expressions]

Le vendredi 7 mai 2021 à 22:41:36 UTC+2, Nils Bruin a écrit : > On Friday, May 7, 2021 at 12:37:41 PM UTC-7 emanuel wrote: > [ Snip... ] Unless you advise me not to do so (and explain why), I’ll file a ticket on >> this issue, propose a branch replacing those null strings with a single >>

[sage-devel] Re: Preliminary bug [Re: Boolean expressions]

Le vendredi 7 mai 2021 à 17:54:51 UTC+2, Nils Bruin a écrit : On Friday, May 7, 2021 at 6:07:30 AM UTC-7 emanuel wrote: > >> Both maxima interfaces mangle Maxima’s boolean operators *printing*. >> The evaluation of a Maxima boolean expression gives nonsensical results >> in Sage. Using the

[sage-devel] Re: Preliminary bug [Re: Boolean expressions]

--> Exiting back to Sage <-- HTH, ​ Le vendredi 7 mai 2021 à 15:07:30 UTC+2, Emmanuel Charpentier a écrit : > Both maxima interfaces mangle Maxima’s boolean operators *printing*. > The evaluation of a Maxima boolean expression gives nonsensical results in > Sage. Using the pexpec

[sage-devel] Re: Preliminary bug [Re: Boolean expressions]

--> Exiting back to Sage <-- ``` HTH, Le vendredi 7 mai 2021 à 15:07:30 UTC+2, Emmanuel Charpentier a écrit : > Both maxima interfaces mangle Maxima’s boolean operators *printing*. > The evaluation of a Maxima boolean expression gives nonsensical results in > Sage. Using the

[sage-devel] Preliminary bug [Re: Boolean expressions]

Both maxima interfaces mangle Maxima’s boolean operators *printing*. The evaluation of a Maxima boolean expression gives nonsensical results in Sage. Using the pexpect interface : sage: ME=maxima sage: ME("foo: a and (b or c)") aand(borc) This also happens in Maxima’s *printing*: sage:

[sage-devel] Re: Boolean expressions

Dear Nils, Thanks for your answers. Note : overloading & and | for SR is probably not a good idea ; it would be way too easy to write problematic code such as : sage: a < x < b # This "double comparison" is legal in Sage... a < x # but gives a "flow control"

[sage-devel] Re: Boolean expressions

Dear Nils, Thank you for this hindsight full response. A couple remarks below : Le jeudi 6 mai 2021 à 08:06:18 UTC+2, Nils Bruin a écrit : > "and" and "or" in python are not logical operators -- they are flow > control for expressions; much like the " ... if ... else ..." expression > is.

[sage-devel] Boolean expressions

At least Sympy, Maxima and Mathematica can treat boolean expressions as other expressions. Maxima : : (%i1) display2d:false; (%o1) false (%i2) foo: a and b; (%o2) a and b (%i3) bar: subst([a=(%pi>3), b=(%pi<4)], foo); (%o3) %pi > 3 and %pi < 4 (%i4) is(bar); (%o4) unknown (%i5) bar, ev;

Re: [sage-devel] Re: Downgrade R to optional? See #31409.

On Tarc#31409 , E. Madison Bray proposed to make R an optionalpackage only on Windows (which should be made possible by an upcoming patch of Matthias Koeppe). I replied : Arghhh… This would be a documentation nightmare (explaining why a ticket is

[sage-devel] Re: Downgrade R to optional? See #31409.

I'm torn : - On one hand, R provides a lot (understatement...) of non-trivial numerical and data-processing-related algorithms. A large part of this "lot" comes from user-written packages (17273 as of today), covering an unparalleled range of use cases ; a lot of them have no

Re: [sage-devel] Re: A possibly nasty bug : expand() isn't absorbing.

This is also discussed in this thread <https://groups.google.com/g/sage-devel/c/sY3zh-pq8T4> (which seems to have somewhat derived...) Le mercredi 17 février 2021 à 13:17:52 UTC+1, Emmanuel Charpentier a écrit : > Le mercredi 17 février 2021 à 12:01:28 UTC+1, dim...@gmail.co

Re: [sage-devel] Re: A possibly nasty bug : expand() isn't absorbing.

Le mercredi 17 février 2021 à 12:01:28 UTC+1, dim...@gmail.com a écrit : > No current sage dev knows pynac code, and it is a can of worms. > All of the following are worrysome tickets: > > https://trac.sagemath.org/ticket/30688 > https://trac.sagemath.org/ticket/31411 >

  1   2   3   4   5   6   >