[sage-devel] Re: trac server very slow to respond

The issue seems over now. Le lundi 29 novembre 2021 à 11:38:37 UTC+1, Eric Gourgoulhon a écrit : > Hi, > > This morning, git pull from git://trac.sagemath.org/sage.git is very > slow. It succeeds eventually, but after ten or so minutes, while there > seems to be no issue w

[sage-devel] trac server very slow to respond

Hi, This morning, git pull from git://trac.sagemath.org/sage.git is very slow. It succeeds eventually, but after ten or so minutes, while there seems to be no issue with my internet connection. Am I the only one experiencing this? Eric. -- You received this message because you are

[sage-devel] New videos on manifolds in Sage

Hi, Christian Bär (Institut für Mathematik, Postdam) has posted a series of very nice introductory videos on manifolds in SageMath: https://www.youtube.com/playlist?list=PLnrOCYZpQUuJlnQbQ48zgGk-Ks1t145Yw A link to them has been added to https://sagemanifolds.obspm.fr/documentation.html

Re: [sage-devel] Re: Sage no longer working in Binder

Le vendredi 1 octobre 2021 à 09:44:48 UTC+2, Eric Gourgoulhon a écrit : > Le jeudi 30 septembre 2021 à 17:53:46 UTC+2, wst...@gmail.com a écrit : > >> My understanding is that the Sage-9.3 and Sage-9.4 binaries are broken >> on a large number of machines due to an issue

Re: [sage-devel] Re: Sage no longer working in Binder

Le jeudi 30 septembre 2021 à 17:53:46 UTC+2, wst...@gmail.com a écrit : > My understanding is that the Sage-9.3 and Sage-9.4 binaries are broken > on a large number of machines due to an issue with how openblas was > built. You probably have to use a sage-9.2 docker container, or wait > for

[sage-devel] Re: Sage no longer working in Binder

The above error message has been obtained by clicking on the Binder button in the notebook https://nbviewer.jupyter.org/github/sagemanifolds/SageManifolds/blob/master/Notebooks/SM_basic_Schwarzschild.ipynb Le jeudi 30 septembre 2021 à 11:03:07 UTC+2, Eric Gourgoulhon a écrit : > The full er

[sage-devel] Re: Sage no longer working in Binder

The full error message is Launching server... Launch attempt 1 failed, retrying... Launch attempt 2 failed, retrying... Launch attempt 3 failed, retrying... Internal Server Error Le jeudi 30 septembre 2021 à 10:50:23 UTC+2, Eric Gourgoulhon a écrit : > Hi, > > Apart from Sage's Doc

[sage-devel] Sage no longer working in Binder

Hi, Apart from Sage's Docker image being still stuck to 9.3.beta8 (issue discussed at https://groups.google.com/g/sage-devel/c/fUpSEHwR5VQ/m/YVmsBSOyCAAJ), a new issue has appeared: one cannot run Sage at all in Binder, even with the 9.3.beta8 image. Every attempt fails at the "Launching

Re: [sage-devel] problem with paralell build

Le mercredi 29 septembre 2021 à 13:13:34 UTC+2, john.c...@gmail.com a écrit : > Mine is also 1024, so perhaps it is a common default (I have ubuntu > 20.04.3 LTS, and the only ulimit thing I set to a non-default value is > 'ulimit -c 0'). Perhaps the build instructions could mention this as >

[sage-devel] Re: Outdated instructions in "git the hard way"

Also the title of that section, "Git the hard way", should be changed. It should rather be "Git the *standard* way" IMHO. Eric. Le mercredi 8 septembre 2021 à 00:47:44 UTC+2, Nils Bruin a écrit : > On: > > https://doc.sagemath.org/html/en/developer/manual_git.html > > it is suggested to

[sage-devel] Re: workers for docker images on gitlab

Hi, Le jeudi 1 avril 2021 à 09:54:22 UTC+2, Frédéric Chapoton a écrit : > it would be good to make sure that sage 9.3 will have a correct docker > image. > But since recently (9.3.b9), the gitlab setting seems no longer to work. > This is certainly related: as of today, the latest Docker image

[sage-devel] Re: Please test

Le mardi 30 mars 2021 à 06:41:47 UTC+2, Kwankyu Lee a écrit : > Hi all, > > The patch in the ticket > > https://trac.sagemath.org/ticket/31536 > > aims to solve a few problems in displaying sage objects in jupyter > environment. > > As we are fear of any regressions, please test the patch with

Re: [sage-devel] Re: Replacing %display latex with %display html

Le mardi 23 mars 2021 à 21:40:13 UTC+1, Eric Gourgoulhon a écrit : > Le mardi 23 mars 2021 à 19:37:33 UTC+1, Thierry (sage-googlesucks@xxx) a > écrit : > >> Hi, >> >> On Tue, Mar 23, 2021 at 11:20:05AM -0700, Eric Gourgoulhon wrote: >> > PS: IMHO, things

[sage-devel] Re: Replacing %display latex with %display html

Back to the main point of this thread: I understand that %display latex has some issues (related to MathJax) in its current implementation but I would say that from the *end user* point of view, changing %display latex to %display html might not be a good thing. Indeed %display html sounds

Re: [sage-devel] Re: Replacing %display latex with %display html

, plain text is used Le mercredi 24 mars 2021 à 10:43:40 UTC+1, Eric Gourgoulhon a écrit : > A small update: using the method _latex_ pointed out by Kwankyu, the > implementation of _repr_latex_ in the class SageObject could become: > > def _repr_latex_(self): > try: >

Re: [sage-devel] Re: Replacing %display latex with %display html

# if None is returned, plain text is used Le mardi 23 mars 2021 à 21:49:41 UTC+1, Eric Gourgoulhon a écrit : > Le mardi 23 mars 2021 à 20:28:45 UTC+1, wst...@gmail.com a écrit : > >> Because I created this years before Jupyter started... >> > > Ah yes! > &

Re: [sage-devel] Re: Replacing %display latex with %display html

Le mardi 23 mars 2021 à 20:28:45 UTC+1, wst...@gmail.com a écrit : > Because I created this years before Jupyter started... > Ah yes! it would be great to redo it. > As a starting point, it would suffice to endow the class SageObject with a method _repr_latex_ defined as something like

Re: [sage-devel] Re: Replacing %display latex with %display html

Le mardi 23 mars 2021 à 19:37:33 UTC+1, Thierry (sage-googlesucks@xxx) a écrit : > Hi, > > On Tue, Mar 23, 2021 at 11:20:05AM -0700, Eric Gourgoulhon wrote: > > PS: IMHO, things like %display latex or %display html are hindrances for > > newcome

[sage-devel] Re: Replacing %display latex with %display html

PS: IMHO, things like %display latex or %display html are hindrances for newcomers. Le mardi 23 mars 2021 à 19:13:10 UTC+1, Eric Gourgoulhon a écrit : > Hi, > > Le mardi 23 mars 2021 à 16:49:07 UTC+1, Kwankyu Lee a écrit : > >> Hi all, >> >> Changes by tick

[sage-devel] Re: Replacing %display latex with %display html

Hi, Le mardi 23 mars 2021 à 16:49:07 UTC+1, Kwankyu Lee a écrit : > Hi all, > > Changes by ticket #31536 may cause unexpected regressions in Sage in > jupyter notebook. Please test and leave comments. > > Here is the address: https://trac.sagemath.org/ticket/31536 > May I take the

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

Le dimanche 21 mars 2021 à 19:29:18 UTC+1, dmo...@deductivepress.ca a écrit : > fwiw, I am not seeing the bug: "they previously broke convexity" looks > fine on my computer. (I tried with Firefox and Safari on MacOS 10.15.7.) > Apparently, the issue has disappeared (has been fixed?):

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

Thanks for the reminder. Done for manifolds. I've noticed a possible issue of the wiki server: all texts inside parentheses are rendered in italics without any parenthesis nor white space. See for instance the output of "The Schlegel diagrams are now repaired (they previously broke convexity)"

Re: [sage-devel] pynac maintainership

Le lundi 18 janvier 2021 à 22:57:31 UTC+1, kcrisman a écrit : > Thanks for all your work on this over the years, Ralf, it has been greatly > appreciated! > > Yes, many thanks! Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

[sage-devel] Re: missing docker images of sagemath

Le mardi 8 décembre 2020 à 09:33:03 UTC+1, Frédéric Chapoton a écrit : > the build for 9.3.beta3 has passed successfully, so there should be a > docker for that, and a docker for develop that should point to the same. Cool, thank you Frédéric! On the page

Re: [sage-devel] Making the package jmol optional

Le lundi 7 décembre 2020 à 15:01:58 UTC+1, dim...@gmail.com a écrit : > On Mon, Dec 7, 2020 at 10:02 AM Eric Gourgoulhon > wrote: > > > > > > > > Le lundi 7 décembre 2020 à 10:57:22 UTC+1, Eric Gourgoulhon a écrit : > >> > >> Indeed

Re: [sage-devel] Making the package jmol optional

Le lundi 7 décembre 2020 à 11:22:36 UTC+1, dim...@gmail.com a écrit : > isn't it something to ask the .js upstream for, a non-interactive png > export? > > Yes this sounds like something to do. I remember however that there was a discussion about some security issues in such a process. Maybe

Re: [sage-devel] Making the package jmol optional

Le lundi 7 décembre 2020 à 12:51:46 UTC+1, Sébastien Labbé a écrit : > At some point in time, tachyon was used to generate static images of > Graphics3D objects. Why isn't not possible to use tachyon for the images in > the doc instead of jmol? > Technically, this is easy: it suffices to

Re: [sage-devel] Making the package jmol optional

Le lundi 7 décembre 2020 à 10:57:22 UTC+1, Eric Gourgoulhon a écrit : > Le lundi 7 décembre 2020 à 10:26:46 UTC+1, François Bissey a écrit : > >> >> >> > On 7/12/2020, at 10:25 PM, Antonio Rojas wrote: >> > >> > Is there any reason for

Re: [sage-devel] Making the package jmol optional

Le lundi 7 décembre 2020 à 10:26:46 UTC+1, François Bissey a écrit : > > > > On 7/12/2020, at 10:25 PM, Antonio Rojas wrote: > > > > Is there any reason for not making jsmol optional too? Isn't three.js > the default renderer these days? > > > > three.js still cannot be used to build the

[sage-devel] Re: parallel compilation does not work anymore

Le mercredi 2 décembre 2020 à 14:20:56 UTC+1, vdelecroix a écrit : > Dear all, > > For the 9.3.beta2 release the command > > $ MAKE="make -j3" make build > > does not compile the Cython code of the sagelib in parallel. > This slows down a lot the build of the library. I am sure > when it

Re: [sage-devel] cocalc and sagemath webpage

Le samedi 21 novembre 2020 à 10:58:17 UTC+1, dim...@gmail.com a écrit : > On Fri, Nov 20, 2020 at 10:32 AM Eric Gourgoulhon > > > > Well, this is more an issue with that particular repository ( > https://github.com/sagemath/more-sagemath-tutorials) than with Binder and &g

Re: [sage-devel] cocalc and sagemath webpage

Le vendredi 20 novembre 2020 à 11:58:52 UTC+1, Eric Gourgoulhon a écrit : > PS: btw, I am also +1 with Dima proposal regarding the web page. > PPS: I forgot to mention (this is so obvious to me), that CoCalc is a great tool; I am using it for my research, to share notebooks with collabo

Re: [sage-devel] cocalc and sagemath webpage

PS: btw, I am also +1 with Dima proposal regarding the web page. Le vendredi 20 novembre 2020 à 11:32:26 UTC+1, Eric Gourgoulhon a écrit : > Le vendredi 20 novembre 2020 à 10:40:07 UTC+1, dim...@gmail.com a écrit : > >> >> there are potentially more ways to run sagemath on

Re: [sage-devel] cocalc and sagemath webpage

Le vendredi 20 novembre 2020 à 10:40:07 UTC+1, dim...@gmail.com a écrit : > > there are potentially more ways to run sagemath online, e.g. it used > to be possible at some point to run it in mybinder, IIRC. > Now it's broken, however: > https://github.com/sagemath/sage-binder-env/issues/9 > >

[sage-devel] Re: Backslash line continuation broken in Sage 9.2

2020 à 12:50:03 UTC+1, Eric Gourgoulhon a écrit : > Le lundi 16 novembre 2020 à 12:08:36 UTC+1, Eric Gourgoulhon a écrit : > >> A culprit might be https://trac.sagemath.org/ticket/28974, since it >> deals with the preparser and backslashes, but I am not sure... >> >>

[sage-devel] Re: Backslash line continuation broken in Sage 9.2

Le lundi 16 novembre 2020 à 12:08:36 UTC+1, Eric Gourgoulhon a écrit : > A culprit might be https://trac.sagemath.org/ticket/28974, since it deals > with the preparser and backslashes, but I am not sure... > > Sorry it cannot be that one, since it has been merged only in Sa

[sage-devel] Backslash line continuation broken in Sage 9.2

In Sage 9.2, attempting to define a callable symbolic expression with a backslash line continuation yields a syntax error: sage: f(x) = x \ :+ 1 File "", line 1 __tmp__=var("x"); f =

[sage-devel] Re: "Real Field" -> "Real Floating-point Field"

A big +1 from my side. Eric. Le mercredi 14 octobre 2020 à 08:28:08 UTC+2, vdelecroix a écrit : > Dear all, > > I would like to discuss the patchbomb at > > https://trac.sagemath.org/ticket/24523 > > The ticket hopes to change the string representation from > "Real Field with XX bits of

[sage-devel] Re: possible bug with manifolds

I cannot reproduce the issue with Sage 9.1. Are you sure that you have a working install of Sage? Le dimanche 27 septembre 2020 à 11:03:25 UTC+2, abhic...@gmail.com a écrit : > > I was following this >

[sage-devel] Re: Proposal to add "tox" as a standard package - entry point for testing and linting

+1 Eric. Le lundi 7 septembre 2020 à 23:18:34 UTC+2, Matthias Koeppe a écrit : > tox (https://tox.readthedocs.io/en/latest/) is a popular package that is > used by a large number of Python projects as the standard entry point for > testing and linting. > > Sage 9.1 started to use tox for

[sage-devel] Re: f(sqrt(x)) yields sqrt(x) for f(x) = x^2

Le samedi 15 août 2020 à 18:23:12 UTC+2, Nils Bruin a écrit : > > > so at least it's not the name of the variable itself. Callable expressions > aren't the problem. The behaviour is mirrored in variable substitution > already: > > It's most likely some silly bug in pynac. That requires

[sage-devel] Re: f(sqrt(x)) yields sqrt(x) for f(x) = x^2

') sage: f(sqrt(y)) y Le samedi 15 août 2020 à 16:36:55 UTC+2, Eric Gourgoulhon a écrit : > Hi, > > I know that sqrt in Sage is terribly buggy (cf. e.g. the recent thread > https://groups.google.com/g/sage-devel/c/h

[sage-devel] f(sqrt(x)) yields sqrt(x) for f(x) = x^2

Hi, I know that sqrt in Sage is terribly buggy (cf. e.g. the recent thread https://groups.google.com/g/sage-devel/c/h50LZVLVQI4/m/fSWpSpYEAwAJ) , but this one seems horrible: sage: f(x) = x^2 sage: f(sqrt(x)) sqrt(x) The composition of f with everything else than sqrt looks OK: sage:

[sage-devel] Re: Nice mess in multiple derivatives...

I forgot to mention: this is a transfert from a sage-support message by Emmanuel: https://groups.google.com/d/msg/sage-support/5M50BRbHy2k/5jRYMnf7AQAJ Le samedi 1 août 2020 12:19:45 UTC+2, Eric Gourgoulhon a écrit : > > > > Le samedi 1 août 2020 10:06:47 UTC+2, Emmanuel Charpen

[sage-devel] Fwd: Nice mess in multiple derivatives...

Le samedi 1 août 2020 10:06:47 UTC+2, Emmanuel Charpentier a écrit : > > Consider : > > sage: f=function("f") > sage: m=var("m", domain="integer") > sage: assume(m>0) > > Sage follows the Maxima convention for multiple derivation d^n/dx^n f(x) > is diff(f(x),x,n) : > > sage: diff(sin(x),x,3) >

[sage-devel] Re: Adding support for discrete differential geometry for SAGE?

Hi, Le lundi 20 juillet 2020 01:17:39 UTC+2, Travis Scrimshaw a écrit : > > Hi Siddharth, >That sounds like a good idea. > +1 ! What you will need to do is create a number of tickets to add in the > corresponding functionality. Once you have a proposal (which you can ask > questions on

[sage-devel] Re: Split into interpreter and python package to facilitate development

Hi Tobias, Le dimanche 31 mai 2020 14:49:46 UTC+2, Tobias Diez a écrit : > > > For now I came up with the following workaround, which works but feels > like a huge hack: Create a file `/src/sage/test.py` with the following > content. You can then run this file using the local python (e.g. >

[sage-devel] Re: sage -pip install in a system-wide install

Thank you Vincent, Matthias and Michael for your answers! Best regards, Eric. -- 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] sage -pip install in a system-wide install

Hi, During the release of the latest version of the Sage package kerrgeodesic_gw https://pypi.org/project/kerrgeodesic-gw/ early this week, various Ubuntu users have complained that sage -pip install kerrgeodesic_gw returns the error sage-run received unknown option: -pip This occurs when

[sage-devel] Re: Build Error with Sage9.rc2 on Ubuntu 20.04

> Someone posted a new list of all packages that have to be preinstalled on the > system som time ago, but I cannot found it again. Could this be the issue > here? > > Is https://wiki.sagemath.org/prerequisites/Ubuntu the list you are looking for? Maybe it should be updated for Ubuntu

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

Le mardi 14 avril 2020 20:36:38 UTC+2, Matthias Koeppe a écrit : > > Let's prepare https://wiki.sagemath.org/ReleaseTours/sage-9.1 > by collaborative editing. > Thanks a lot! I've added a threejs entry and will add a manifold one later on. Btw, shouldn't there be a link from

[sage-devel] Re: Generation of sample points for log-scale plots

Hi, Le jeudi 16 avril 2020 06:21:42 UTC+2, Blair Mason a écrit : > > Hello all, > > Should generate_plot_points() be modified to log-sample on plots where the > x scale is logarithmic? I'd be willing to write the patch up but I'd like > to know that it would be desired behavior before I do so.

[sage-devel] Re: Where to propose addition of change log and updates of documentation ...

Le samedi 11 avril 2020 20:54:11 UTC+2, Matthias Koeppe a écrit : > > I have just revived https://wiki.sagemath.org/ReleaseTours with > rudimentary pages https://wiki.sagemath.org/ReleaseTours/sage-9.0 and > https://wiki.sagemath.org/ReleaseTours/sage-9.1, for collaborative > editing. > >

[sage-devel] Re: FAQ: building Sage on debian or ubuntu

Thank you Dima! I've updated https://wiki.sagemath.org/prerequisitesUbuntu accordingly. Eric. -- 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] Re: 3d arrows

Le lundi 24 février 2020 18:59:42 UTC+1, Eric Gourgoulhon a écrit : > > Le lundi 24 février 2020 17:24:48 UTC+1, kcrisman a écrit : >> >> I can't remember where people were talking about arrows in 3d with Sage >> being broken in Sage 9, >> > > This is ht

[sage-devel] Re: 3d arrows

Le lundi 24 février 2020 17:24:48 UTC+1, kcrisman a écrit : > > I can't remember where people were talking about arrows in 3d with Sage > being broken in Sage 9, > This is https://trac.sagemath.org/ticket/29206 Eric. -- You received this message because you are subscribed to the Google

[sage-devel] Re: Tip: easy input of math/unicode symbols

Hi Emmanual, Le vendredi 21 février 2020 20:39:31 UTC+1, Emmanuel Charpentier a écrit : > > But such variable names may cause havoc in a \LaTeX output. Consider: > > sage: var("λ") > λ > > This works > > sage: latex(λ^2) > λ^{2} > > Ahem: the rendition of λ is ... "λ", which pdflatex doesn't

Re: [sage-devel] Unable to build sage after git trac config

Hi, Le jeudi 30 janvier 2020 04:06:02 UTC+1, Vipul Gupta a écrit : > > > Yeah Sage works fine after that. But I wanted to contribute to sage and > therefore config my git trac account as mentioned in the this link > https://doc.sagemath.org/html/en/developer/git_trac.html > > Welcome to Sage

[sage-devel] Re: FYI introductory Sage book in Portuguese

Le samedi 18 janvier 2020 23:28:45 UTC+1, kcrisman a écrit : > > I don't think has been announced here yet, my apologies if it has been. > +++ > Check out this book: https://sagectu.com.br/ > Nice-looking website, of course complete with download links as well. > Particularly useful will be

Re: [sage-devel] Re: Build of 9.0 failed at R

se, gfortran --version returns GNU Fortran (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Eric. > On Sun, 12 Jan 2020, 15:36 Eric Gourgoulhon, > wrote: > >> From the log files, a difference between your system and mine is that >> your Linux kernel is 5.0.0-37-generic, while min

[sage-devel] Re: Build of 9.0 failed at R

ric. Le dimanche 12 janvier 2020 15:19:59 UTC+1, Eric Gourgoulhon a écrit : > > PS: I am attaching my log file for R. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emai

[sage-devel] Re: Build of 9.0 failed at R

Hi Malcolm, I have the same OS as you (Ubuntu 18.04) and I could build 9.0 (as well as 9.1.beta0) without any trouble. If I compare the file r-3.6.2.log resulting from the build of R on my system with yours, they are pretty similar until these lines in your r-3.6.2.log: making pretty.d from

Re: [sage-devel] Re: drop python2 compatibility in 9.1 ?

Le mardi 7 janvier 2020 14:35:45 UTC+1, Dima Pasechnik a écrit : > > Why 8.9? One can build 9.0 with python2 just fine. > > Yes I know, but I was speaking about the time and energy to actually build those and distribute them. IMHO, there are more pressing issues, like the handling of ipython7

Re: [sage-devel] Re: drop python2 compatibility in 9.1 ?

Le mardi 7 janvier 2020 13:25:04 UTC+1, E. Madison Bray a écrit : > > On Mon, Jan 6, 2020 at 7:30 PM Eric Gourgoulhon > wrote: > > > > On the other hand, for the end user the major backwards-incompatibility > change already happened: a Python 2-only piece of code w

Re: [sage-devel] Re: drop python2 compatibility in 9.1 ?

Le lundi 6 janvier 2020 14:21:56 UTC+1, E. Madison Bray a écrit : > > > I agree with Nils. There should be at least a one release deprecation > period. Also, while I don't think we use any kind of real semantic > versioning, I think we should name a Python 3-only release 10.0 as > it's a very

[sage-devel] Re: drop python2 compatibility in 9.1 ?

+1 for dropping Python 2 compatibility in Sage 9.1 Eric. -- 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...@googlegroups.com. To view this

[sage-devel] Re: Simple integral raises AttributeError

Le mercredi 4 décembre 2019 20:14:48 UTC+1, Emmanuel Charpentier a écrit : > > The old (> 5 years...) Trac#16816 > ticket is germane... > Thanks for pointing out this ticket! In #28842 , I propose a quick fix until

Re: [sage-devel] Simple integral raises AttributeError

Le mercredi 4 décembre 2019 18:37:15 UTC+1, Dima Pasechnik a écrit : > > sure, please open a ticket. > This is now https://trac.sagemath.org/ticket/28842 Please review. Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Simple integral raises AttributeError

Hi, In Sage 9.0.beta8 we have sage: a = var('a') sage: integrate(1/(x^4 + x^2 + a), x) ... AttributeError: 'RootSum' object has no attribute '_sage_' The same error occurs in Sage 8.9, but not in Sage 8.8 (and below). In Sage 8.8, we have instead: sage: a = var('a') sage: integrate(1/(x^4 +

[sage-devel] Re: Weird behaviour at the interface Sage/Maxima for symbolic functions

Le lundi 2 décembre 2019 14:50:41 UTC+1, Eric Gourgoulhon a écrit : > > > Thanks for your feedback. IMHO, this is a very serious bug, since in > practice it prevents from using any option (like nargs or latex_name) in > function(), for in actual calculations, sooner or

[sage-devel] Re: Weird behaviour at the interface Sage/Maxima for symbolic functions

Le lundi 2 décembre 2019 04:00:52 UTC+1, Nils Bruin a écrit : > > On Sunday, December 1, 2019 at 2:45:21 PM UTC-8, Eric Gourgoulhon wrote: >> >> >> Is this a known bug? >> >> The bug is certainly expected. As you demonstrate, a symbolic function > has it

[sage-devel] Weird behaviour at the interface Sage/Maxima for symbolic functions

Hi, Consider the following code with Sage 9.0.beta7: sage: x, y = var('x y', domain='real') sage: phi = function('phi', latex_name=r'\varphi') sage: s = phi(x, y).simplify() sage: s phi(x, y) It looks good, but it is not: sage: s.subs({phi(x, y): 1}) phi(x, y) The failure of the substitution

Re: [sage-devel] Re: Significant slowdown of basic arithmetic

Le samedi 23 novembre 2019 20:34:51 UTC+1, John H Palmieri a écrit : > > It's not actually Sage 8.9 vs. 9.0, it is? Rather it's Python 2 vs. Python > 3. > I confirm this: since at least Sage 8.5, Python 3 is roughly 10% slower than Python 2 in running the manifold doctests via sage -tp --long

[sage-devel] Re: Compiling with Catalina

Le samedi 9 novembre 2019 21:55:09 UTC+1, Rob Gross a écrit : > > One other point: at least for me, the result of > > ? euler_gamma > > is not good: > >Nearly all expressions are created by calling >new_Expression_from_*, but we need to make sure this at least does >not leave

Re: [sage-devel] Re: Switch to Python 3 by default

Le mardi 5 novembre 2019 11:34:55 UTC+1, Salvatore Stella a écrit : > > On a side note: is jmol going to be replaced? If so, should we just ignore > the issue? > > Jmol has been replaced by three.js as Sage's default 3d viewer in Sage 9.0.beta0, cf.

[sage-devel] Re: Ticket #15555 (Murnaghan-Nakayama formula)

Le samedi 2 novembre 2019 13:56:47 UTC+1, Keren Shao a écrit : > > It looks like #1 is still open (and I cannot find any implementation > from the documentation.) Can anyone confirm its status with me? > > Also, I am trying understand how to contribute, say a script for > Murnaghan-Nakayama

Re: [sage-devel] Re: sage.plot.graphics.GraphicsArray no longer available?

Le mercredi 30 octobre 2019 00:25:53 UTC+1, Eric Gourgoulhon a écrit : > > > OK, this is now https://trac.sagemath.org/ticket/28675 > I've turned https://trac.sagemath.org/ticket/28675 into a deprecation notice for GraphicsArray import from sage.plot.graphics. This seems

Re: [sage-devel] Re: sage.plot.graphics.GraphicsArray no longer available?

Le mardi 29 octobre 2019 23:49:41 UTC+1, William a écrit : > > On Tue, Oct 29, 2019 at 1:37 PM Eric Gourgoulhon > wrote: > > > > Do you think it's necessary to add a redirect import for GraphicsArray > from sage.plot.graphics? We can easily make a new ticket to

[sage-devel] Re: sage.plot.graphics.GraphicsArray no longer available?

Le mardi 29 octobre 2019 21:17:02 UTC+1, Eric Gourgoulhon a écrit : > > Le mardi 29 octobre 2019 19:19:51 UTC+1, William a écrit : >> >> >> It's (obviously) likely that at least one person did that. This is part >> of the public API of Sage, so it would be goo

[sage-devel] Re: sage.plot.graphics.GraphicsArray no longer available?

Le mardi 29 octobre 2019 19:19:51 UTC+1, William a écrit : > > > It's (obviously) likely that at least one person did that. This is part > of the public API of Sage, so it would be good if it were deprecated before > removal (or just left in via a one-liner redirect import). > Sorry about

[sage-devel] Re: Problems launching jupyter browser window and threejs browser window

Le dimanche 27 octobre 2019 15:36:45 UTC+1, jplab a écrit : > > Hi everyone, > > I wanted to test the following ticket on sage 9.0beta2: > > https://trac.sagemath.org/ticket/28658 > > So I wrote the following in the terminal: > > sage: p = polytopes.icosahedron() > sage: p.plot() > Launched html

[sage-devel] Re: Manifolds: Using Multiprocessing with Functions causes Error

This is unfortunately a known bug: parallelism does not work with symbolic functions. The ticket devoted to this issue is https://trac.sagemath.org/ticket/27492 Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

[sage-devel] Re: Switch to Python 3 by default

Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit : > > Maybe I missed it, but I didn't find a ticket for that. I think now would > be a good time to flip the switch, though. Any thoughts? > +1 Eric. -- You received this message because you are subscribed to the Google

[sage-devel] Re: sage.plot.graphics.GraphicsArray no longer available?

Le mercredi 23 octobre 2019 19:46:10 UTC+2, Pong a écrit : > > Sorry for jumping the gun. > > The improved version is > sage.plot.multigraphics.GraphicsArray(array) > > > http://doc.sagemath.org/html/en/reference/plotting/sage/plot/multigraphics.html#module-sage.plot.multigraphics > > For the

[sage-devel] Re: Manifolds: 'set_restriction' Behaviour

The method set_restriction() has probably been implemented only for cases where the domain of a is a strict subset of the domain of b. When both domains coincide, instead of using b.set_restriction(a), I would have written sage: b = a.copy() However, since M is a subset of itself,. the

[sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

This is to close this poll properly. The clearly expressed opinions are - in favor of making three.js the default: 6 (8 if one adds mine as well as that of Dima, who positively reviewed the ticket) - in favor of keeping Jmol as the default: 0 Consequently, the branch of the ticket implementing

[sage-devel] Re: Machine Learning people apparently built a symbolic integrator

Thanks for sharing! This looks very promising. I hope we have it in Sage some day. Eric. Le vendredi 27 septembre 2019 17:06:31 UTC+2, Dima Pasechnik a écrit : > > https://openreview.net/pdf?id=S1eZYeHFDS > > I wish they had code available... > -- You received this message because you are

[sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

Le lundi 23 septembre 2019 13:51:23 UTC+2, Eric Gourgoulhon a écrit : > > - 3d plots rendered with three.js can be publicly shared via > nbviewer.jupyter.org, contrary to those rendered with Jmol, which > appear as > blank spaces, cf. this test notebook: > > https:/

[sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

Le lundi 23 septembre 2019 13:51:23 UTC+2, Eric Gourgoulhon a écrit : > Indeed, thanks to the work of Paul Masson, the three.js 3d viewer is doing > a > very good job in displaying Sage 3d plots, as you can see in these examples > taken from Sage reference's manua

Re: [sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

Le lundi 23 septembre 2019 21:41:55 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : > > > Also, the java issue is now fixed, which also means that jmol is still > maintained. > > Yes. To be 100% clear: this poll is not about deprecating Jmol, but about making three.js the default. Eric. --

[sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

Le lundi 23 septembre 2019 14:53:32 UTC+2, Emmanuel Charpentier a écrit : > > > >- The "minor transparency issues" he mentions may deprive the >resulting plot of part of its mathematical meaning (for example, the plot >of a sphere and a cone can curently clobber the display of the

[sage-devel] Poll: three.js as the default 3d viewer in Sage

Dear Sage-dev, This is a poll to make three.js (https://threejs.org/) the default 3d viewer in Sage, in replacement of Jmol (https://sourceforge.net/projects/jmol/). Indeed, thanks to the work of Paul Masson, the three.js 3d viewer is doing a very good job in displaying Sage 3d plots, as you can

[sage-devel] Re: inconsistency in computation of differential of a map between manifolds

Le mercredi 28 août 2019 21:29:29 UTC+2, Eric Gourgoulhon a écrit : > > > You are perfectly right: "check" would be more appropriate than "verbose" > in this context. > I'll open a ticket for this and make "check=True" the default. > This is no

[sage-devel] Re: inconsistency in computation of differential of a map between manifolds

Hi Simon, Le mercredi 28 août 2019 07:07:03 UTC+2, Simon King a écrit : > > > Is the option really called "verbose=True"? Not "check=True", like in > most other cases? > > You are perfectly right: "check" would be more appropriate than "verbose" in this context. I'll open a ticket for this

[sage-devel] Re: inconsistency in computation of differential of a map between manifolds

Le mardi 27 août 2019 16:51:20 UTC+2, Andreas Hermann a écrit : > > I am sorry, but this is a stupid mistake. The function defined via > set_inverse() is not the inverse function since the first entry of atan2 is > by definition the y-coordinate. If one swaps u and v in atan2 then > everything

[sage-devel] Re: [gentoo) insufficient memory for the JRE to continue.

Le samedi 3 août 2019 22:45:43 UTC+2, Timo Kaufmann a écrit : > > It's been a while, but now we are seeing a similar issue here[1]. In our > case it fails the doctests, seems to be jmol running out of memory. > Another motivation for https://trac.sagemath.org/ticket/22408 Eric. -- You

[sage-devel] Re: Introducing a new feature: graphics insets

ease... IMHO, this functionality is useful in plots for scientific papers. For instance, we have used it in this article <https://www.aanda.org/articles/aa/pdf/2019/07/aa35406-19.pdf> (in which all plots have been produced with Sage ;-) ). Eric. Le vendredi 24 mai 2019 17:41:44 UTC+2, Eric Gourgoulho

Re: [sage-devel] delay 8.8?

Le samedi 22 juin 2019 16:02:36 UTC+2, Julian Rüth a écrit : > > There shouldn't be a problem with using the latest 8.8rc in binder. > > On Saturday, June 22, 2019 at 1:54:26 PM UTC+2, Eric Gourgoulhon wrote: >> >> [...] It would be nice if 8.8 is released by then. Otherwi

Re: [sage-devel] delay 8.8?

Hi, Le vendredi 21 juin 2019 23:12:47 UTC+2, E. Madison Bray a écrit : > > > Sometimes I have heard there is a conference or something for which a > release is needed. If that is the case someone should speak up. > Well, I have a talk on 11 July at the 22nd International Conference on

[sage-devel] Fwd: Updating Sage documentation presentation

Le mercredi 19 juin 2019 14:31:05 UTC+2, saad khalid a écrit : > > Hi all: > > The sage documentation hosted online (eg. > http://doc.sagemath.org/html/en/reference/index.html ) looks very old. To > me at least, it makes the software seem ancient, and I believe it puts off > younger new

<    1   2   3   4   5   6   7   >