[sage-devel] Re: VOTE: Use "CI Fix" label for merging into continuous integration runs

[Eric Gourgoulhon]

+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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2daa8156-3a9d-4879-a31d-fc0f18e5dbb4n%40googlegroups.com.

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

[Eric Gourgoulhon]

-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 is a serious regression and definitely a 
blocker IMHO: are we willing to release a version of SageMath that cannot 
be used without an internet connection?

Eric.

Le mercredi 28 février 2024 à 07:45:03 UTC+1, Kwankyu Lee a écrit :

> Hi, 
>
> Here I withdraw the early premature "giving up" on my recent proposal, 
> since afterwards there were some positive comments. Hence I open a voting 
> for 
>
> Proposal: 
>
> 1. Do not use "blocker" label for Issues, as "blocker" means to delay the 
> release.
> 2. Instead use "critical" label for a very serious and urgent Issue.
> 3. A PR fixing the "critical" Issue will likely get the "blocker" label.
> 4. Old Issues converted from trac with "critical" label will get the 
> "major" label instead. 
>
> Voting will end when there is no new vote for a week.
>
> This is a simple majority voting (following the standard on sage-devel 
> proposal)!
>
> A positive vote is for all parts of the Proposal. So if you do not like 
> any of (1) -- (4), cast a negative vote (-1).
>
>
> Happy voting! 
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a2c85e9b-ac46-49d7-8385-f568fddfa236n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Hi Nils,

Le vendredi 16 février 2024 à 04:37:28 UTC+1, Nils Bruin a écrit :

On Thursday 15 February 2024 at 17:02:14 UTC-8 Dima Pasechnik wrote:

but that's sphinx (Python), not jupyter.

I see. The page I linked to is from Jupyter{book} which is, despite the 
similarity in name, not the jupyter notebook server. 


You are not alone: I did exactly the same thing ;-) After a google-search 
for "jupyter custom mathjax", I ended up on the same page and for a second 
I thought it contains the solution, before realizing that this page is 
dedicated to the Sphinx generation of a book about Jupyter, not to Jupyter 
itself. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/23ad2776-e5ae-4fcf-ba90-a186cc54b27an%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le jeudi 15 février 2024 à 13:36:46 UTC+1, Dima Pasechnik a écrit :

A possible solution does not involve changing Sage/Jupyter config. It's  by 
capturing http requests to CDN and replacing them with the local resources.


Thank you Dima! Could you indicate how to do this? (looks quite technical 
to me)
 


See e.g. 
https://discourse.jupyter.org/t/running-voila-without-internet/13823/3

where this is proposed for another MathJax-dependent project.


I am quite surprised that Jupyter does not offer a simple way to do this... 
In some countries, being offline is unfortunately more common than being 
online. 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a5970a85-4335-43fe-b79d-8eddd9065c07n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le jeudi 15 février 2024 à 11:20:40 UTC+1, Kwankyu Lee a écrit :

With the previous version of Jupyterlab shipped with Sage 10.2, the 
system's MathJax was used. 

Can't we tweak the new Jupyterlab shipped with Sage 10.3 to use the 
system's MathJax as well?


We don't do that. Perhaps tweaking is more severe sin than sage vendoring 
jupyter, from Dima's viewpoint :-)  


Yes of course. By "tweaking" I actually meant "configuring". 
 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/88946834-d097-4aff-a793-a059e3f3d771n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le jeudi 15 février 2024 à 04:54:42 UTC+1, Kwankyu Lee a écrit :


I checked again on mac. Yes, jupyterlab (and notebook 7 as well) of Sage 
10.3.beta8 fails in loading mathjax 2.7.7. (Before it worked because of the 
cache, I guess)


OK, thanks for the feedback!  Hence this is not a Ubuntu-specific issue. 
 

It seems that jupyterlab(notebook 7) only uses mathjax cdn. (As far as I 
know, jupyter never used system mathjax or sage mathjax). 

I guess that before notebook 7, jupyter vendored mathjax with it, but after 
notebook 7, jupyter only uses cdn.  


This sounds a strange policy from Jupyter, since it prevents people from 
using notebooks offline. Are you sure about this? 
 

Hence there is nothing to do on sage side. 


With the previous version of Jupyterlab shipped with Sage 10.2, the 
system's MathJax was used. Can't we tweak the new Jupyterlab shipped with 
Sage 10.3 to use the system's MathJax as well? 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/95e22d5b-090e-4e9d-9500-e3d31deb5349n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 18:21:04 UTC+1, Matthias Koeppe a écrit :

You  may recall that we use jupyterlab_mathjax2 because of the discussion 
in https://github.com/sagemath/sage/pull/36129#issuecomment-1729218062


Thanks for reminding me about this. Then I guess the question is: why 
Jupyterlab in Sage 10.3.beta8 is using MathJax 2.7.7 (available only 
online) and not the system's MathJax (2.7.9) ? Again, there was no such 
issue with Sage 10.2. 
 
 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5c672a08-3f82-4e55-a2f5-795558b386cbn%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 15:09:27 UTC+1, Eric Gourgoulhon a écrit :

The partial conclusion is thus: 

- Sage 10.2 uses Ubuntu 22.04's MathJax (v2.7.9), so there is no issue when 
the computer is offline.
- for some reason, Sage 10.3.beta* refuses to use Ubuntu 22.04's MathJax 
and the MathJax 3.2.0 shipped with Sage is not installed/used either. 
  


Sage's MathJax 3.2.0 is definitely installed in my Sage 10.3.beta8 root 
tree for if I look at the locally generated reference manual (i.e. 
local/share/doc/sage/html/en/reference/index.html), the math formulas there 
are rendered by MathJax 3.2.0 (as one can see by right-clicking on them and 
selecting "About MathJax"); this works even in the offline mode.

So it appears that Sage's MathJax 3.2.0 is used for the documentation but 
not for Jupyter/Jupyterlab notebooks.
  

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e22cc827-23ea-4446-a297-5738caf59dd5n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 15:39:05 UTC+1, Kwankyu Lee a écrit :

On Wednesday, February 14, 2024 at 10:55:41 PM UTC+9 Eric Gourgoulhon wrote:

Le mercredi 14 février 2024 à 14:51:01 UTC+1, Eric Gourgoulhon a écrit :

What is puzzling is that MathJax 3.2.0 seems to have been successfully 
installed in the Sage tree during the install of Sage 10.3.beta*, cf. the 
attached log (SAGE_ROOT/logs/pkgs/mathjax-3.2.0.log), 


Well, maybe not: the log contains:

Package 'mathjax' is currently not installed
No legacy uninstaller found for 'mathjax'; nothing to do


The log below this says mathjax 3.2.0 was installed. 


Indeed, but the indicated CPU time looks very short.
FWIW, here is the output of 
find . -name "*mathjax*"
in my Sage 10.3.beta8 root tree:

./build/pkgs/mathjax
./build/pkgs/jupyterlab_mathjax2
./src/doc/en/reference/spkg/mathjax.rst
./src/doc/en/reference/spkg/jupyterlab_mathjax2.rst
./logs/pkgs/jupyterlab_mathjax2-4.0.0.log
./logs/pkgs/mathjax-3.2.0.log
./upstream/mathjax-3.2.0.tar.gz
./upstream/jupyterlab_mathjax2-4.0.0-py3-none-any.whl
./local/var/lib/sage/venv-python3.10/var/lib/sage/installed/jupyterlab_mathjax2-4.0.0
./local/var/lib/sage/venv-python3.10/var/lib/sage/wheels/jupyterlab_mathjax2-4.0.0-py3-none-any.whl
./local/var/lib/sage/venv-python3.10/var/lib/sage/scripts/jupyterlab_mathjax2
./local/var/lib/sage/venv-python3.10/share/jupyter/lab/schemas/@jupyterlab/mathjax-extension
./local/var/lib/sage/venv-python3.10/share/jupyter/nbconvert/templates/base/mathjax.html.j2
./local/var/lib/sage/venv-python3.10/share/jupyter/labextensions/@jupyterlab/mathjax2-extension
./local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/jupyterlab/schemas/@jupyterlab/mathjax-extension
./local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/jupyterlab_mathjax2-4.0.0.dist-info
./local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/jupyterlab_mathjax2
./local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sphinx/ext/__pycache__/mathjax.cpython-310.pyc
./local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sphinx/ext/mathjax.py
./local/var/lib/sage/installed/mathjax-3.2.0
./local/share/mathjax
./local/share/mathjax/mathjax
./local/share/giac/doc/mathjax.sty
./local/share/doc/sage/doctrees/en/reference/spkg/jupyterlab_mathjax2.doctree
./local/share/doc/sage/doctrees/en/reference/spkg/mathjax.doctree
./local/share/doc/sage/html/en/reference/spkg/_sources/mathjax.rst.txt
./local/share/doc/sage/html/en/reference/spkg/_sources/jupyterlab_mathjax2.rst.txt
./local/share/doc/sage/html/en/reference/spkg/jupyterlab_mathjax2.html
./local/share/doc/sage/html/en/reference/spkg/mathjax.html

and that of find . -name "*mathjax-3*" :

./logs/pkgs/mathjax-3.2.0.log
./upstream/mathjax-3.2.0.tar.gz
./local/var/lib/sage/installed/mathjax-3.2.0

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0645f7e5-9f09-49ee-a53a-6c7249a9b396n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 14:51:01 UTC+1, Eric Gourgoulhon a écrit :


More precisely, the Ubuntu 22.04's libjs-mathjax is version 2.7.9. 
When the computer is online and I right-click on "About MathJax" in a 
displayed cell, I get "MathJax v2.7.7", which is not the system version...


If I do the same thing when the computer is offline with Sage 10.2, I get 
"MathJax v2.7.9", which is the system version. 
The partial conclusion is thus: 

- Sage 10.2 uses Ubuntu 22.04's MathJax (v2.7.9), so there is no issue when 
the computer is offline.
- for some reason, Sage 10.3.beta* refuses to use Ubuntu 22.04's MathJax 
and the MathJax 3.2.0 shipped with Sage is not installed/used either. 
   

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8a163bfb-0b2c-483a-a5da-faf8b62361a4n%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 14:51:01 UTC+1, Eric Gourgoulhon a écrit :

What is puzzling is that MathJax 3.2.0 seems to have been successfully 
installed in the Sage tree during the install of Sage 10.3.beta*, cf. the 
attached log (SAGE_ROOT/logs/pkgs/mathjax-3.2.0.log), 


Well, maybe not: the log contains:

Package 'mathjax' is currently not installed
No legacy uninstaller found for 'mathjax'; nothing to do


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6e4b03e6-1d4f-4287-8668-81f5b46046ebn%40googlegroups.com.

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 14:18:20 UTC+1, Eric Gourgoulhon a écrit :

Le mercredi 14 février 2024 à 14:13:04 UTC+1, Dima Pasechnik a écrit :

For off the grid working with MathJax, you need it locally installed. It 
might be that by default it doesn't happen, and MathJax is dynamically 
loaded from the net.


The Ubuntu packages libjs-mathjax and fonts-mathjax are installed on my 
system. 


More precisely, the Ubuntu 22.04's libjs-mathjax is version 2.7.9. 
When the computer is online and I right-click on "About MathJax" in a 
displayed cell, I get "MathJax v2.7.7", which is not the system version...
What is puzzling is that MathJax 3.2.0 seems to have been successfully 
installed in the Sage tree during the install of Sage 10.3.beta*, cf. the 
attached log (SAGE_ROOT/logs/pkgs/mathjax-3.2.0.log), but apparently it is 
not used in the notebook. 


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5d5e1a02-edf2-4efa-9bec-be674e851f4fn%40googlegroups.com.
Using cached file /home/eric/sage/10.3/upstream/mathjax-3.2.0.tar.gz
mathjax-3.2.0

Setting up build directory for mathjax-3.2.0
Finished extraction
No patch files found in ../patches

Host system:
Linux tensor 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.4.0-1ubuntu1~22.04' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) 

Package 'mathjax' is currently not installed
No legacy uninstaller found for 'mathjax'; nothing to do
src/mathjax -> /home/eric/sage/10.3/local/var/tmp/sage/build/mathjax-3.2.0/inst/home/eric/sage/10.3/local/share/mathjax

real	0m0.053s
user	0m0.009s
sys	0m0.041s
Moving package files from temporary location /home/eric/sage/10.3/local/var/tmp/sage/build/mathjax-3.2.0/inst to /home/eric/sage/10.3/local
Successfully installed mathjax-3.2.0
Deleting temporary build directory
/home/eric/sage/10.3/local/var/tmp/sage/build/mathjax-3.2.0
Finished installing mathjax-3.2.0

Re: [sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Le mercredi 14 février 2024 à 14:13:04 UTC+1, Dima Pasechnik a écrit :

For off the grid working with MathJax, you need it locally installed. It 
might be that by default it doesn't happen, and MathJax is dynamically 
loaded from the net.


The Ubuntu packages libjs-mathjax and fonts-mathjax are installed on my 
system. Moreover, on the same computer, MathJax display works well when 
offline with Sage 10.2. 


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8ef574c7-7156-4f67-849a-c0dfb4b3bd10n%40googlegroups.com.

[sage-devel] No MathJax display in Sage 10.3.beta notebooks when offline

[Eric Gourgoulhon]

Hi,

While working on a Sage 10.3.beta  notebook in a train without any internet 
connection, I've noticed that there is no LaTeX rendering via MathJax, 
neither in the markdown cells nor in the output cells within the scope of  
%display latex. There is no such issue with Sage 10.2 and I've opened 
https://github.com/sagemath/sage/issues/36914
for this. 

Apparently, the problem arises with Ubuntu 22.04, but not with macOS. It 
would be nice to have more tests, possibly on various OS, to identify the 
issue. Thanks for your feedback!

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4ab5d581-0ba9-4e30-9ad1-06250d66053an%40googlegroups.com.

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

[Eric Gourgoulhon]

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

Eric. 
Le vendredi 9 février 2024 à 11:57:08 UTC+1, Georgi Guninski a écrit :

> hi,
>
> var('n')
> sum((4*n+1)/factorial(n),n,1,oo)
>
> TypeError: 'NoneType' object is not callable
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/824cbae6-d30d-4d27-8e08-38f787978bc4n%40googlegroups.com.

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

[Eric Gourgoulhon]

Le vendredi 17 novembre 2023 à 10:14:54 UTC+1, Dima Pasechnik a écrit :



On 17 November 2023 04:35:53 GMT, Matthias Koeppe  
wrote: 
>Or we just let pillow use a system libjpeg if it finds one.


This would probably be the easiest solution: I cannot imagine a system 
without libjpeg...
 



With a dummy package we can have doctests, 
with #optional tag, checking that this all works. 


What is exactly a "dummy package"? Is it something that requires a system 
package ?  Is it complicated to set up and maintain? 
Otherwise, we could just require libjpeg as a prerequisite to build Sage 
from source and add it to the list
https://doc.sagemath.org/html/en/installation/source.html#prerequisites

In any case, at the moment, PIL is barely usable in the Sage 10.2.rc3  
notebook, even if no jpeg image is manipulated. For instance,  the 
following code considers only a png image:

from PIL import Image
plot(sin(x)).save("fig.png")
img = Image.open("fig.png")
img
  
and yields

ValueError: Could not save to JPEG for display

There was no such issue in previous versions of Sage (e.g. 10.1). 
As a consequence, the following public notebook 
https://nbviewer.org/github/sagemanifolds/SageManifolds/blob/master/Notebooks/SM_black_hole_rendering.ipynb
is broken in Sage 10.2.rc3 and there are probably many of those. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9d7e2a72-7c1a-4077-90dc-db03615cf914n%40googlegroups.com.

[sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

[Eric Gourgoulhon]

Hi All,

Pillow provides the Python Imaging Library (PIL)
https://pillow.readthedocs.io/en/stable/
and is a standard package in Sage. 

Now, in Sage 10.2.rc3, the following code

g = plot(sin(x)) # to generate a png figure
g.save("fig.png")  #
from PIL import Image
img = Image.open("fig.png")
img_rgb = img.convert("RGB")
img_rgb.save("fig.jpg")

returns

OSError: encoder jpeg not available

This is actually not surprising since the file
SAGE_ROOT/build/pkgs/pillow/spkg-install.in
contains the line:

PILLOW_CONFIG_SETTINGS="-C debug=true -C jpeg=disable 
$PILLOW_CONFIG_SETTINGS"

Is there any reason for "jpeg=disable" ? 
Providing PIL without jpeg support seems quite weird...
This issue is not new and was already noticed already 5 years ago:
https://ask.sagemath.org/question/43298

A side effect of this is that the IPyhon  rendering of PIL Images via the 
rich output mechanism is broken in Sage 10.2.rc3 (but, for some reasons, 
not in Sage 10.1): 
in a Jupyter notebook, typing

img = Image.open("fig.png")
img

does display the image but after an error message terminating by 
ValueError: Could not save to JPEG for display
There is no such error message in Sage 10.1

If we agree to restore jpeg support in Pillow, I have prepared a branch 
that does this for Sage 10.2 (simply suppressing the option "jpeg=disable"):
https://github.com/egourgoulhon/sage/tree/pillow_jpeg
and I am happy to submit a PR for this.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e1a2bf34-d3e5-492b-942c-33b1fc8c3254n%40googlegroups.com.

[sage-devel] Re: Sage 9.5 won't launch nor install (any version ? ) on debian testing/sid and ubuntu 23.10

[Eric Gourgoulhon]

Hi, 

In case it might help for the Ubuntu install, you may take a look at this 
page:
https://sagemanifolds.obspm.fr/install_ubuntu.html

Best wishes,

Eric. 

Le mardi 7 novembre 2023 à 13:00:55 UTC+1, Laurent Bakri a écrit :

> Hi all,
>
> I am using Debian Testing (now "Sid" because I was wondering if it could 
> help; it doesn't) and Ubuntu (23.10). Since a recent (a few months ago?) 
> upgrade of Singular, SageMath won't launch on my Debian machines (laptop 
> and desktop) or on my recently upgraded Ubuntu. I'm encountering the 
> following error:
>
> *Error in sys.excepthook: Traceback (most recent call last): File 
> "/usr/lib/python3.11/pathlib.py", line 1251, in is_dir return 
> S_ISDIR(self.stat().st_mode) ^ AttributeError: 'str' object has no 
> attribute 'stat' See the file debug-launching-sage.log.*
>
> So I tried to install Sage from source on my Debian desktop, but it won't 
> compile because it fails to build Brial (something related to libboost, if 
> I understand correctly):
>
> *"/../libbrial/include/polybori/common/traits.h:26:10: fatal error: 
> boost/preprocessor/cat.hpp: No such file or directory 26 | #include 
> *
>
> I'm not sure which direction I should take now. Historically, it has been 
> easy because there were some "vanilla" binaries available for Linux. 
> Currently, I am limited to using Sage 9.2, which, if I understand 
> correctly, is the last version that comes with a "generic" compiled version.
>
> Any help would be greatly appreciated. 
>
> Regards, 
>
> Laurent
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bd4d37eb-3346-4845-8061-87f781781826n%40googlegroups.com.

[sage-devel] Re: SageMath 10.1 for macOs ARM randomly fails to compute the Riemann/Ricci tensor or Ricci scalar when using threads

[Eric Gourgoulhon]

Hi, 

Le lundi 2 octobre 2023 à 13:42:29 UTC+2, Alejandro Marino Vaquero 
Avilés-Casco a écrit :

When running sagemath release version 10.1 in macOs for the arm 
architecture (the target tested has a M2 processor) with multiple threads, 
the calculation of the Riemann tensor, the Ricci tensor or the Ricci scalar 
normally fails, although sometimes it randomly success. Executing single 
thread solves the problem. 


This is the issue 
https://github.com/sagemath/sage/issues/35580
regarding Sage parallel computations on macOS.
Many macOS users are facing it and I hope it will be solved someday...

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a068f844-3b2f-49fb-8aa7-d0107140b731n%40googlegroups.com.

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

[Eric Gourgoulhon]

+1 for deprecation

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/28931800-c7fd-4aa2-88d7-90569d737bf4n%40googlegroups.com.

Re: [sage-devel] Discussion and poll: should Sage Integers have a backslash operator?

[Eric Gourgoulhon]

+ 1 for getting rid of the preparsing of \

It is particularly annoying when typing (usually long) expressions like

f(x) = x + \ 
   1
in an input cell of a Jupyter notebook. If the \ is followed by a blank 
space, one gets 

Cell In [22], line 1 
__tmp__=var("x"); f = symbolic_expression(x + * BackslashOperator() * 
).function(x)
SyntaxError: invalid syntax

which is particularly disturbing for a new user!

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d397d13d-1765-43b1-ac55-17ccc764196fn%40googlegroups.com.

Re: [sage-devel] Make ipympl a standard package

[Eric Gourgoulhon]

PS: I've just updated the notebook for checking that long math expressions 
are wrapped. 

Le mardi 19 septembre 2023 à 21:06:42 UTC+2, Eric Gourgoulhon a écrit :

> Hi Kwankyu,
>
> Le mardi 19 septembre 2023 à 20:56:51 UTC+2, Kwankyu Lee a écrit :
>
> Hi Eric,
>
> I see no interaction in the "test_display" notebook rendered by nbviewer.
>
>
> This is a limitation of nbviewer.  
>
> If you provide the latest version of the notebook, I can put it into the 
> notebooks directory
> of  https://github.com/sagemath/sage-binder-env/tree/dev. Where is the 
> notebook? 
>
>
> The notebook is here:
>
> https://github.com/egourgoulhon/SageMathTest/blob/master/Notebooks/test_display.ipynb
>  
> (you can see it by clicking on the Github icon in the nbviewer top right 
> menu).
>
> Best wishes,
>
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d4e35b37-43f9-493d-9223-09dee9fb1ce4n%40googlegroups.com.

Re: [sage-devel] Make ipympl a standard package

[Eric Gourgoulhon]

Hi Kwankyu,

Le mardi 19 septembre 2023 à 20:56:51 UTC+2, Kwankyu Lee a écrit :

Hi Eric,

I see no interaction in the "test_display" notebook rendered by nbviewer.


This is a limitation of nbviewer.  

If you provide the latest version of the notebook, I can put it into the 
notebooks directory
of  https://github.com/sagemath/sage-binder-env/tree/dev. Where is the 
notebook? 


The notebook is here:
https://github.com/egourgoulhon/SageMathTest/blob/master/Notebooks/test_display.ipynb
 
(you can see it by clicking on the Github icon in the nbviewer top right 
menu).

Best wishes,

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2f2fb791-f62a-43b5-b4e7-57620002bbb0n%40googlegroups.com.

[sage-devel] Make ipympl a standard package

[Eric Gourgoulhon]

Hi Sage dev,

In PR #36129 , which is 
devoted to the upgrade to Jupyter Notebook 7, we are proposing to make 
ipympl a standard package.
ipympl  is a pip-installable package that 
enables using the interactive features of Matplotlib in Jupyter Notebook 
and Jupyterlab, via the magic %matplotlib widget or %matplotlib ipympl, 
cf. https://matplotlib.org/ipympl/
Here is an example of use in Sage:
https://nbviewer.org/github/egourgoulhon/SageMathTest/blob/master/Notebooks/test_display.ipynb
With this package, matplotlib.pyplot (the standard "plt") becomes 
interactive (e.g. one can zoom  and scroll with the mouse), which is quite 
nice. 

Please give your opinion about making ipympl a standard package. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fe46cb71-7031-4254-be81-ec1d29900348n%40googlegroups.com.

[sage-devel] Re: Voting: Block-scoped optional tag and the keyword

[Eric Gourgoulhon]

I vote for (A)

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1931486a-b228-402b-b2b7-42945e3fd18dn%40googlegroups.com.

Re: [sage-devel] Creating a github team

[Eric Gourgoulhon]

Thanks for your reply. 

Le mardi 7 février 2023 à 14:33:04 UTC+1, David Roe a écrit :
  4. When a component tag is added to a PR (or a new PR created with a 
component set), if there is no reviewer already requested then the bot will 
request review from someone on that component team (eventually we may 
refine this process based on what lines are being modified in the PR).  
Details on how a person is chosen are still to be worked out, but we think 
it's helpful to have a single person responsible rather than a large group.
  5. If a reviewer declines or if a review is not given within a week (this 
duration can be up for discussion), the bot will request review from 
another member of that component team.

I would rather favor a mode in which the bot sends a notification to the 
whole team at each tagged PR, instead of picking members one per one, so 
that any team member that is interested by the PR, feels competent and has 
the time to do the review can do it. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3de741ca-1c8f-461c-9df8-0eaf95ca8444n%40googlegroups.com.

[sage-devel] Creating a github team

[Eric Gourgoulhon]

Hi,

Thanks again for all the hard work for the github migration!

I would like to create a team "Manifolds" of https://github.com/sagemath, 
with sufficient permissions so that I can add users to it. How shall I 
proceed? Are there any team creation request on the github interface or 
should some sagemath admin do it?

Maybe a preliminary question: do we want to create github teams to organize 
Sage development by topics?

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1120db7e-9536-4b06-8d43-b1d1a920de3dn%40googlegroups.com.

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

[Eric Gourgoulhon]

Le lundi 6 février 2023 à 10:47:28 UTC+1, dim...@gmail.com a écrit :

Can you edit it now? 

Yes, thanks!

Eric. 
 
I'd removed "Restrict editing to users in teams 
with push access only" 

Please also note that GitHub wikis are git repos. You can clone them 
in the usual way (git clone 
https://github.com/sagemath/sage.wiki.git), push, etc. 

> 
> 
> 
> Do you know when/how we can get these permissions? Sage Days 117 have 
started this morning and it would be nice if we could get them this week. 
> 
> 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+...@googlegroups.com. 
> To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/db72f382-f4e2-4bbf-8377-5335f98d37f3n%40googlegroups.com.
 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9527a2ae-4a0f-4c58-9d58-501c1da20aa2n%40googlegroups.com.

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

[Eric Gourgoulhon]

Le lundi 6 février 2023 à 09:50:58 UTC+1, Kwankyu Lee a écrit :
It is now in 

https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8

But we don't have permissions to edit it yet.


 Do you know when/how we can get these permissions? Sage Days 117 have 
started this morning and it would be nice if we could get them this week. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/db72f382-f4e2-4bbf-8377-5335f98d37f3n%40googlegroups.com.

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

[Eric Gourgoulhon]

Le lundi 6 février 2023 à 09:50:58 UTC+1, Kwankyu Lee a écrit :
It is now in 

https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8

OK, very good.
I've updated
https://wiki.sagemath.org/ReleaseTours
accordingly. 

Eric. 
 

But we don't have permissions to edit it yet.

On Monday, February 6, 2023 at 5:38:46 PM UTC+9 Eric Gourgoulhon wrote:
Hi, 

Since trac logins are now disabled, it seems that we cannot edit the 9.8 
release tour.

Eric.

Le samedi 7 janvier 2023 à 09:02:07 UTC+1, Matthias Koeppe a écrit :
It's time to work on the release tour for the upcoming 9.8 release 
https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c55787fb-1474-420e-980c-a60a40057633n%40googlegroups.com.

Re: [sage-devel] Migration to GitHub complete

[Eric Gourgoulhon]

Le lundi 6 février 2023 à 08:25:30 UTC+1, GMS a écrit :

Huge thanks to everybody involved.

+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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/dab95e3b-da9e-4f1a-82e2-9777cca2bb65n%40googlegroups.com.

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

[Eric Gourgoulhon]

Hi, 

Since trac logins are now disabled, it seems that we cannot edit the 9.8 
release tour.

Eric.

Le samedi 7 janvier 2023 à 09:02:07 UTC+1, Matthias Koeppe a écrit :

> It's time to work on the release tour for the upcoming 9.8 release 
> https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f1f3bc86-ded0-436f-bcde-9afe0eaa6464n%40googlegroups.com.

Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

[Eric Gourgoulhon]

Le lundi 30 janvier 2023 à 15:07:36 UTC+1, dim...@gmail.com a écrit :
OK, it should be read-only now (for pushing, ticket 
creating/modifying, other state-changing admin) 

Thank you Dima!
 
Logins still work though, but they have no effect on anything, as far 
as I can see. 

Please let me know if for some reason you still can modify things! 


It seems that, once logged in, one can still modify a ticket comment, see 
https://trac.sagemath.org/ticket/30525#comment:106

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a327a441-4153-4173-b6b7-abc219ec7932n%40googlegroups.com.

[sage-devel] Re: Multiple warnings in sagemath on default fedora 37

[Eric Gourgoulhon]

Hi, 

Le vendredi 20 janvier 2023 à 06:26:38 UTC+1, Georgi Guninski a écrit :

sage: integrate(floor(x)^2,x) 
// Giac share root-directory:/usr/share/giac/ 
// Giac share root-directory:/usr/share/giac/ 
Added 0 synonyms 
x*floor(x)^2 

I get this one with Sage 9.8.beta7 built from source on Ubuntu. So it is 
not a Fedora packaging issue. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/34708034-f732-4b4a-9682-13039658ca56n%40googlegroups.com.

[sage-devel] Re: SageMath docker image + mybinder.org

[Eric Gourgoulhon]

PS: I confirm that your solution works for the notebooks of 
https://sagemanifolds.obspm.fr/examples.html
The start up is quite long, but if one is patient enough, it works!

Le jeudi 17 novembre 2022 à 09:41:11 UTC+1, Eric Gourgoulhon a écrit :

> Hi,
> Le mercredi 16 novembre 2022 à 23:53:41 UTC+1, de...@benjamin-hackl.at a 
> écrit :
>
>> Hey all,
>>
>> I really liked the way of making code accessible via a repository or gist 
>> containing a bunch of notebooks together with a simple Dockerfile that has 
>> not much more than "FROM sagemath/sagemath:version" in it -- but this is 
>> something that broke down a while ago (
>> https://github.com/sagemath/sage-binder-env/issues/9, couldn't find a 
>> trac ticket).
>>
>> Now, I don't speak Jupyter well enough to understand why it doesn't still 
>> work, but I've found that if, instead of using notebook from SageMath's 
>> venv, one installs Python 3 + Jupyter separately in the container and links 
>> the SageMath kernel to it, the docker images *can* still be used with 
>> mybinder. I've left details here: 
>> https://github.com/sagemath/sage-binder-env/issues/9#issuecomment-1317769194,
>>  
>> mybinder link: 
>> https://mybinder.org/v2/gist/behackl/a5d25c901ec557565f99331b130f09a2/HEAD
>> .
>>
>
> Thanks for sharing! It's very nice that we can have mybinder + Sage 
> working again! 
>
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e746ca39-eb07-4b67-b5d5-d963963c4083n%40googlegroups.com.

[sage-devel] Re: SageMath docker image + mybinder.org

[Eric Gourgoulhon]

Hi,
Le mercredi 16 novembre 2022 à 23:53:41 UTC+1, de...@benjamin-hackl.at a 
écrit :

> Hey all,
>
> I really liked the way of making code accessible via a repository or gist 
> containing a bunch of notebooks together with a simple Dockerfile that has 
> not much more than "FROM sagemath/sagemath:version" in it -- but this is 
> something that broke down a while ago (
> https://github.com/sagemath/sage-binder-env/issues/9, couldn't find a 
> trac ticket).
>
> Now, I don't speak Jupyter well enough to understand why it doesn't still 
> work, but I've found that if, instead of using notebook from SageMath's 
> venv, one installs Python 3 + Jupyter separately in the container and links 
> the SageMath kernel to it, the docker images *can* still be used with 
> mybinder. I've left details here: 
> https://github.com/sagemath/sage-binder-env/issues/9#issuecomment-1317769194, 
> mybinder link: 
> https://mybinder.org/v2/gist/behackl/a5d25c901ec557565f99331b130f09a2/HEAD
> .
>

Thanks for sharing! It's very nice that we can have mybinder + Sage working 
again! 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0b42a6b4-4c22-4226-8d42-812de62b4793n%40googlegroups.com.

[sage-devel] Re: Method 'latex.mathjax_avoid_list()' missing in the official docker image

[Eric Gourgoulhon]

Le mardi 15 novembre 2022 à 23:26:31 UTC+1, Eric Gourgoulhon a écrit :

>
> The methods latex.add_to_mathjax_avoid_list and latex.mathjax_avoid_list 
> have been removed in Sage 9.3. So your docker image must be based on an old 
> version of Sage (current stable version is 9.7). 
>

Sorry I read your message too fast: these methods missing means that your 
docker image has a version of  Sage more recent than 9.2...

 

> In https://doc.sagemath.org/html/en/reference/misc/sage/misc/latex.html 
> one can read
> *This module focuses on using LaTeX for printing. For the use of LaTeX for 
> rendering math in HTML by MathJax, see MathJax 
> <https://doc.sagemath.org/html/en/reference/misc/sage/misc/html.html#sage.misc.html.MathJax>
>  
> defined in sage.misc.html 
> <https://doc.sagemath.org/html/en/reference/misc/sage/misc/html.html#module-sage.misc.html>.*
> Maybe this can help you. 
> Best wishes,
>
> Eric. 
>
> PS: yes the tutorial must be updated...
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d16ba856-fa20-4e69-9656-7d2e1db3ea7en%40googlegroups.com.

[sage-devel] Re: Method 'latex.mathjax_avoid_list()' missing in the official docker image

[Eric Gourgoulhon]

Le mardi 15 novembre 2022 à 12:28:38 UTC+1, lucca@gmail.com a écrit :

> When using the official docker image, from within a Notebook the
> methods 
>
>- `latex.add_to_mathjax_avoid_list()` 
>- `latex.mathjax_avoid_list`
>
> are missing on the `latex` object.
>
> These should exist, according to the docs: 
> https://doc.sagemath.org/html/en/tutorial/latex.html#customizing-latex-processing
>
> This prevents using renderers other than MathJax to render more 
> complicated LaTeX output, such ones that involve TikZ pictures.
>
> If the method was changed or support for custom latex processing was 
> removed, I'd urge to update the docs. There is no mention of additional 
> package imports or configuration being needed to use these methods.
>
> I will also attach the project im currently working on:
> https://github.com/jimkoen/sagemath-thesis-template/settings
>
> I use a slightly modified docker image, the modifications of which you can 
> see in the repo.
>
> While I can't say for certain, I highly doubt that these have removed 
> these methods.
>

The methods latex.add_to_mathjax_avoid_list and latex.mathjax_avoid_list 
have been removed in Sage 9.3. So your docker image must be based on an old 
version of Sage (current stable version is 9.7). 
In https://doc.sagemath.org/html/en/reference/misc/sage/misc/latex.html one 
can read
*This module focuses on using LaTeX for printing. For the use of LaTeX for 
rendering math in HTML by MathJax, see MathJax 

 
defined in sage.misc.html 
.*
Maybe this can help you. 
Best wishes,

Eric. 

PS: yes the tutorial must be updated...

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/90eb4d5e-3f31-413f-a8ac-90d0fc6b6d95n%40googlegroups.com.

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

[Eric Gourgoulhon]

PS: the loss of text3d is particularly apparent here:
https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/reference/plot3d/sage/plot/plot3d/shapes2.html#sage.plot.plot3d.shapes2.text3d
as compared to
https://doc.sagemath.org/html/en/reference/plot3d/sage/plot/plot3d/shapes2.html#sage.plot.plot3d.shapes2.text3d

Le mercredi 9 novembre 2022 à 22:19:23 UTC+1, Eric Gourgoulhon a écrit :

> Le mercredi 9 novembre 2022 à 06:22:43 UTC+1, Kwankyu Lee a écrit :
>
>> Hi,
>>
>> Trac #34730 rebases sage_autodoc onto the upgraded Sphinx 5.3.0. It is 
>> responsible for formatting Sage objects (functions, classes, etc.) to build 
>> documentation.
>>
>> Please check your favorite sections in our documentation 
>>
>>
>> https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/
>>
>> for any regression due to #34730. 
>>
>
> At first glance, looks good, thanks. 
> Regarding 3D plots, they are rendered with Tachyon, instead of Jmol  for 
> Sage 9.7: compare
>
> https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/reference/plot3d/sage/plot/plot3d/plot3d.html
> with 
>
> https://doc.sagemath.org/html/en/reference/plot3d/sage/plot/plot3d/plot3d.html
> Any reason for this? (the drawback of Tachyon is that we are loosing axes 
> labels, as well as text3d). 
>
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/45c19eb8-3cb0-459b-a16c-e3ccc52aa2d1n%40googlegroups.com.

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

[Eric Gourgoulhon]

Le mercredi 9 novembre 2022 à 06:22:43 UTC+1, Kwankyu Lee a écrit :

> Hi,
>
> Trac #34730 rebases sage_autodoc onto the upgraded Sphinx 5.3.0. It is 
> responsible for formatting Sage objects (functions, classes, etc.) to build 
> documentation.
>
> Please check your favorite sections in our documentation 
>
>
> https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/
>
> for any regression due to #34730. 
>

At first glance, looks good, thanks. 
Regarding 3D plots, they are rendered with Tachyon, instead of Jmol  for 
Sage 9.7: compare
https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/reference/plot3d/sage/plot/plot3d/plot3d.html
with 
https://doc.sagemath.org/html/en/reference/plot3d/sage/plot/plot3d/plot3d.html
Any reason for this? (the drawback of Tachyon is that we are loosing axes 
labels, as well as text3d). 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f46ad344-009c-40bf-be5e-2223120736can%40googlegroups.com.

[sage-devel] Re: Invitation: Weekly 30-minute Sage developer calls on Jitsi

[Eric Gourgoulhon]

Hi,

Le lundi 3 octobre 2022 à 00:32:52 UTC+2, Matthias Koeppe a écrit :

> New times:
>
> Calls for Europe / Africa / Americas:
>
> Monday noon, 12:15pm San Francisco
> Monday afternoon, 3:15pm New York
> Monday evening, 21:15 Paris
> https://meet.jit.si/VibrantTribesBearEver 
> 
>
>
Could there be some error on the time zone or schedule?  It is 21:20 in 
Paris and there is nobody in the room

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/92169af7-7b5c-4690-90e9-32e106efb321n%40googlegroups.com.

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

[Eric Gourgoulhon]

Le samedi 24 septembre 2022 à 13:57:36 UTC+2, kcrisman a écrit :

>
> On another note, I realize that the comment I made 6 years ago after 
> Volker's comment is still relevant:  
> "There's also the non-trivial (though not blocker, probably) issue that 
> zillions of links to trac.sagemath.org would instantly be obsolete"
>
>
This is a good point IMHO. In particular, there are zillions of links to 
Trac from the sage-devel threads.
 

> How long do we want to have Trac still exist, but be read-only?  Obviously 
> we wouldn't take it down right away, but presumably eventually we would 
> need to do so.  
>

As I said earlier, discussions on Trac constitute a very valuable database 
for Sage development. As far as I am concerned, I learned a lot from them. 
It would be a pity to lose them. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e6bac55f-8cd2-4bcd-9308-d411a34d5eben%40googlegroups.com.

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

[Eric Gourgoulhon]

+1 for GitHub

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d3931ec9-d174-484c-95e4-a2ad1686384bn%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Eric Gourgoulhon]

Le jeudi 15 septembre 2022 à 18:34:22 UTC+2, Matthias Koeppe a écrit :

> On Thursday, September 15, 2022 at 9:04:09 AM UTC-7 Matthias Koeppe wrote:
>
>> On Thursday, September 15, 2022 at 6:21:09 AM UTC-7 Eric Gourgoulhon 
>> wrote:
>>
>>> I don't understand why in the post
>>> https://groups.google.com/g/sage-devel/c/QooOF1GLMOs
>>> Matthias asked to remove developer names from 
>>> (1) https://trac.sagemath.org/#AccountNamesMappedtoRealNames
>>> Aren't we loosing information here?
>>> I of course understand there is now 
>>> https://github.com/sagemath/website/blob/master/conf/contributors.xml
>>> and that duplication is the root of all evil, but if a read-only mirror 
>>> of Trac is maintained, the list (1) would be useful to contact a Sage 
>>> developer regarding a specific ticket. 
>>>
>>
>> No, the data is not lost. It is *migrated* to 
>> https://github.com/sagemath/website/blob/master/conf/contributors.xml, 
>> where it will be preserved (including the Trac usernames).
>>
>
> To add to this: The purpose of my request to remove your info after 
> merging it into contributors.xml is the following:
> In 2 weeks or so, I'll bulk-merge the remaining info into 
> contributors.xml; and I will do a cursory review of each item. 
> By removing your already-merged data from the source, you'll save me the 
> time to check which of the information (in contributors.xml or Trac) is 
> more current. 
>

OK, I've then removed my name from the Trac list.  Anyway, since the latest 
upgrade of Trac, real names appear on the tickets, instead of user names, 
which makes the original Trac list less useful.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8ee9a196-011d-461f-b581-dbd33227073fn%40googlegroups.com.

[sage-devel] Re: sage zoom meeting reminder

[Eric Gourgoulhon]

Sorry I cannot make it this time (I am in the train). But next Thursday 
should be OK. 
Best wishes,

Eric. 

Le jeudi 15 septembre 2022 à 16:54:32 UTC+2, wst...@gmail.com a écrit :

> Reminder -- that 30 minute Sage zoom meeting thing that Matthias
> organized is happening in a few minutes from right now at
>
> https://ucdavis.zoom.us/j/92371662861?pwd=TDZKR0lKb2xzTGhiM0l3cnFmaGRadz09
>
> (8:15 pacific time to be exact.)
>
> -- 
> William (http://wstein.org)
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/070288ea-12c5-4f24-a8e4-066417b35575n%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Eric Gourgoulhon]

Le jeudi 15 septembre 2022 à 15:32:22 UTC+2, dim...@gmail.com a écrit :

>
>
> On Thu, 15 Sep 2022, 14:21 Eric Gourgoulhon,  wrote:
>
>> I would like to ask about a point that does not seem to have been 
>> discussed before (apologies if it was):
>> If the migration to Gihub takes place, would there remain somewhere a 
>> read-only copy of Trac? more precisely, of all the Trac tickets? 
>>
>
> yes, this is the plan, to migrate all trac tickets to GitHub issues. There 
> are some technical issues involving issues getting correct (i.e. correctly 
> mapped to GitHub accounts) authors, hopefully resolved with help of GitHub 
> support,
> but apart from this we are not too far getting the migration done. (the 
> git tree is there on a github mirror repo, so links to branches will be 
> pointing there). Attachments will be imported and hosted somewhere, too.
>
> a read-only copy of trac will be around for a while, to make sure it all 
> went well, but I don't expect a strong need to keep it forever.
>
>
 Thanks for your prompt answer.

what's not clear there?
>
>
The description of 
https://github.com/sagemath/trac-to-github
says
"This script migrates milestones, issues, and wiki pages from Trac to 
GitHub."
What about tickets?

Your answer made it more clear. Thanks. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/134ab1cc-2569-47d0-b57d-8aa81be492fen%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Eric Gourgoulhon]

I would like to ask about a point that does not seem to have been discussed 
before (apologies if it was):
If the migration to Gihub takes place, would there remain somewhere a 
read-only copy of Trac? more precisely, of all the Trac tickets? The 
numerous discussions there constitute a valuable database, certainly useful 
for future Sage code development. 
In this respect, I don't understand why in the post
https://groups.google.com/g/sage-devel/c/QooOF1GLMOs
Matthias asked to remove developer names from 
(1) https://trac.sagemath.org/#AccountNamesMappedtoRealNames
Aren't we loosing information here?
I of course understand there is now 
https://github.com/sagemath/website/blob/master/conf/contributors.xml
and that duplication is the root of all evil, but if a read-only mirror of 
Trac is maintained, the list (1) would be useful to contact a Sage 
developer regarding a specific ticket.  

There is mention of "conversion of Trac tickets and the Trac wiki to 
Github" at 
https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b
which might cover the point raised above, but this is not clear to me.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9f76d868-d5fe-4219-b1f8-829af95c6c07n%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Eric Gourgoulhon]

Le mardi 13 septembre 2022 à 07:30:23 UTC+2, David Roe a écrit :

>
> Here's a proposal on a timeline for making a decision (I welcome feedback 
> from anyone who thinks this is too fast or too slow).
>
> * We spend another few days discussing pros and cons and refining the 
> proposed workflows.
> * I'll volunteer to collate the arguments that have been made into a list 
> of pros and cons together with a concrete proposal, and we can send out an 
> email in a separate thread announcing a vote later this week.  
> * The deadline for voting will be one week from the announcement (so, late 
> next week).
> * If the consensus of the community is to switch to github, then a smaller 
> group can proceed with implementation (I'm also willing to be involved in 
> that effort).
>

+1 for this proposal. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/02148649-81f9-4838-b28f-a086e27b9667n%40googlegroups.com.

[sage-devel] Re: BROADCAST MESSAGE

[Eric Gourgoulhon]

Le jeudi 8 septembre 2022 à 09:03:53 UTC+2, Frédéric Chapoton a écrit :

> I can still modify the comments. It may be a matter of permissions. If 
> somebody else confirms, one will have to check.
>

I've just checked that I'm still able to edit my comments.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/88a9fff5-6206-43c2-bc25-c3657055f80en%40googlegroups.com.

[sage-devel] Re: BROADCAST MESSAGE

[Eric Gourgoulhon]

Thank you so much Frédéric at al. for all the work in setting up the new 
Trac!

Eric.

Le dimanche 4 septembre 2022 à 09:32:42 UTC+2, Frédéric Chapoton a écrit :

> Trac 1.2 comes with various changes, including display of full names and 
> internationalisation. You may want to look in your user preferences to 
> customize some of these if you prefer.
>
> Le dimanche 4 septembre 2022 à 01:32:35 UTC+2, Kwankyu Lee a écrit :
>
>> Trac is now in version 1.2. Thanks!
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fe54559d-4a26-4243-a7c8-2b97fe877d2dn%40googlegroups.com.

[sage-devel] Issue with the Dependencies field in Trac pages

[Eric Gourgoulhon]

Hi,

Maybe this is related with the recent restart of Trac: the ticket numbers 
in the "Dependencies" field of a ticket are no longer clickable, nor 
colored. An example is
https://trac.sagemath.org/ticket/30229

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6be65a1a-666b-458a-b4a6-f25a61b58d0an%40googlegroups.com.

[sage-devel] Re: Reducing the size of one of the plots placed in a graphicsarray

[Eric Gourgoulhon]

PS: see also 
https://doc.sagemath.org/html/en/reference/plotting/sage/plot/plot.html#sage.plot.plot.multi_graphics

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/07f742a2-141b-4888-a732-fb5786eb1ba1n%40googlegroups.com.

[sage-devel] Re: Reducing the size of one of the plots placed in a graphicsarray

[Eric Gourgoulhon]

Use multi_graphics instead of graphics_array:
ga = multi_graphics([(p, (0, 0, 0.7, 0.7)), (q, (0.65, 0.2, 0.3, 0.3))])
ga.show()
[image: mg.png]

See 
https://doc.sagemath.org/html/en/reference/plotting/sage/plot/multigraphics.html#sage.plot.multigraphics.MultiGraphics
for details.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/aba09407-6f8b-46c6-ac6b-2453bc944028n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Eric Gourgoulhon]

Le mercredi 24 août 2022 à 03:14:22 UTC+2, Kwankyu Lee a écrit :

> It is embarrassing that  an idea of attaching ".length()" method to a line 
> segment graphics object leads to SageManifolds. We don't need vectors and 
> inner products to compute the length of a line segment.


I agree that it sounds daunting to speak about pseudo-Riemannian manifolds 
for just computing the length of a line segment, but note that, by working 
at the EuclideanSpace level, the end user does not need to know anything 
about the underlying manifold machinery.  See for instance this tutorial: 
https://doc.sagemath.org/html/en/thematic_tutorials/vector_calculus.html

The only complication would be to add the extra line
sage: E = EuclideanSpace(3)
at the beginning of the code For instance, your example at the start of 
this thread would become

sage: E = EuclideanSpace(3)
sage: l = E.line([(1,2,3),(2,2,3)])  # not implemented yet
sage: l.length()
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e8e1cb6a-2fca-4947-afbf-3ed7a1220396n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Eric Gourgoulhon]

Hi, 

Le mercredi 24 août 2022 à 02:18:06 UTC+2, Travis Scrimshaw a écrit :

> In general, I think we are best leaving the drawing classes to just 
> drawing as a separations-of-concerns. 
>

+1
IMHO, line2d and line3d should not be considered as mathematical objects 
(segmented lines in some Euclidean space), but rather as pure graphical 
objects.
 

> It sounds like we need better integration between our algebraic 
> objects/implementations and the drawing/plotting tools. This might include 
> more plot_* functions or specialized mixin-/sub-classes for small 
> dimensional (sub)spaces. Likewise we might want to add some general tools 
> for inner product spaces, such as "ind_closest_point() or 
> shortest_distance(), with an assumption of course that we can do calculus 
> on the vector space.
>

+1
 

>
> As an alternative, if we want to think of objects specifically living in 
> Euclidean space, we have the EuclideanSpace(n) for this with specialized 
> subclasses for 2d and 3d. Perhaps we should implement some of the features 
> you want using objects there, such as line (segment) as a subclass of the 
> curve? For piecewise differentiable curves, this might require some more 
> programming.
>
> Éric, what do you think about adding such things to SageManifolds? Could 
> this be feasible?
>
>
This certainly should be feasible. As you point out, one should introduce a 
subclass of curves for segmented lines in Eudlidean spaces and define a 
length() method for them. More generally, one should introduce a length() 
method for any piecewise differentiable curve in a pseudo-Riemannian 
manifold. This is not implemented yet and certainly should be added to the 
todo list. 

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b551bb01-e95c-4dba-8228-def7f39b3c12n%40googlegroups.com.

[sage-devel] Re: Polling for sphinx background style

[Eric Gourgoulhon]

grayish > detoned > original.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c00a26ee-fd5c-4bf5-a355-effbbd18d02dn%40googlegroups.com.

[sage-devel] Re: Polling for pygments style for our future doc

[Eric Gourgoulhon]

Le jeudi 4 août 2022 à 18:33:27 UTC+2, Eric Gourgoulhon a écrit :

> Thanks for preparing this poll. I vote for 
>
> (1) tango
>

Sorry, I missed the point about the italic. Please change my vote to 

(2) default 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d440018e-7c41-4371-90be-ddb3a4eb9e33n%40googlegroups.com.

[sage-devel] Re: Polling for pygments style for our future doc

[Eric Gourgoulhon]

Thanks for preparing this poll. I vote for 

(1) tango

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ce7be439-422e-4f3d-8ac9-5f23c86229f0n%40googlegroups.com.

[sage-devel] Re: Proposal: make Furo a standard package

[Eric Gourgoulhon]

Le jeudi 4 août 2022 à 03:29:07 UTC+2, Kwankyu Lee a écrit :

> So we propose here to upgrade the Furo package to a standard package. 
> Please vote.


+1
Thanks for working on this.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2d4c3a31-6375-425a-aee3-3a0c6810aa41n%40googlegroups.com.

Re: [sage-devel] Introduction to differentiable manifolds in SageMath

[Eric Gourgoulhon]

Le samedi 25 juin 2022 à 17:31:10 UTC+2, wst...@gmail.com a écrit :

> > There is some issue in the latex display of manifold maps: 
> > ParseError: KaTeX parse error: Undefined control sequence: \mbox at 
> position 96: …thbb{E}^{2} \\ \̲m̲b̲o̲x̲{on}\ A : & \ph… 
>
> Thanks -- I've created this issue in case you're curious about the 
> situation: 
>
> https://github.com/sagemathinc/cocalc/issues/6019 
>
> In particular, I think it would be better if the latex representation 
> output by sage manifolds used "\text{on}" instead of "\mbox{on}"; 
> however, I'll add a workaround in CoCalc so that isn't necessary. 
>

IIRC, I used \mbox instead of \text because \mbox is plain LaTeX, while 
\text requires the package amstext, so I naively thought that \mbox was 
more robust. The katex example shows that it is rather the converse. So 
yes, we may change \mbox to \text. Note that \mbox is quite heavily used in 
all Sage: running 
grep -r '\\mbox'
from src/sage returns 206 lines, among which 34 in src/sage/manifolds.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c103e430-0e8f-4780-a5de-47c5398d7446n%40googlegroups.com.

Re: [sage-devel] Introduction to differentiable manifolds in SageMath

[Eric Gourgoulhon]

Le vendredi 24 juin 2022 à 18:52:00 UTC+2, wst...@gmail.com a écrit :

>
> I also put a copy of these beautiful notebooks here: 
>
> https://cocalc.com/wstein/support/IntroToManifolds 
>
>
Thanks!

There is some issue in the latex display of manifold maps:
ParseError: KaTeX parse error: Undefined control sequence: \mbox at 
position 96: …thbb{E}^{2} \\ \̲m̲b̲o̲x̲{on}\ A : & \ph…

cf. cell [2] of 
https://cocalc.com/wstein/support/IntroToManifolds/files/04Manifold_Spheres.ipynb
 

> This has some pros and cons over nbviewer + mybinder (see 
> https://github.com/sagemathinc/cocalc/issues/6015). 
>
>
>
Indeed, mybinder + Sage is broken at the moment (*). It would be nice to 
have an alternative solution on CoCalc!

Eric. 

(*)  mybinder + Sage used to work quite reasonably (by means of Sage's 
Docker images) some 2 years ago or so. 


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/968791fe-ddb2-4ae5-92e2-1c1b255e5211n%40googlegroups.com.

[sage-devel] Introduction to differentiable manifolds in SageMath

[Eric Gourgoulhon]

Hi, 

Andrzej Chrzeszczyk (Jan Kochanowski University of Kielce, Poland) has 
prepared a series of notebooks introducing differentiable manifolds at the 
textbook level with many examples from Sage and nice figures: 
https://sagemanifolds.obspm.fr/intro_to_manifolds.html

Best wishes,

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cd97217c-6d59-4f30-ae2e-ace681a46ed5n%40googlegroups.com.

[sage-devel] Re: Length of vectors in `plot_vector_field3d()`

[Eric Gourgoulhon]

Le dimanche 19 juin 2022 à 19:11:24 UTC+2, niran...@gmail.com a écrit :

>
> For plot() in sage manifold Reference says:
> **extra_options – extra options for the arrow plot, like linestyle, width 
> or arrowsize (see arrow2d() 
> 
>  
> and arrow3d() 
> 
>  
> for details)
> Eg: width=6
>
> Does this make speed difference or is it due to E.vector_field() ?
>

The speed difference is due to a very different implementation of 
VectorField.plot() as compared to plot_vector_field3d():  at each point of 
the mesh, a tangent vector is created and the method TangentVector.plot() 
is called. See
 
https://doc.sagemath.org/html/en/reference/manifolds/sage/manifolds/differentiable/tangent_vector.html
This is far from optimal but this offers a greater flexibility, for 
instance plotting vector fields on non-rectangular meshes, like vector 
fields on an submanifold or along a curve, see e.g. 
https://sagemanifolds.obspm.fr/gallery.html
for some examples. 
Some performance improvements have been implemented in Sage 9.6 thanks to 
Marius Gerbershagen, cf. 
https://trac.sagemath.org/ticket/33110
but there is room for further significative improvements, by getting rid of 
the call to TangentVector.plot(). This is on the to do list...
Any volunteer is welcome...

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/97194847-5a3e-425e-a3ac-be7d81e9446an%40googlegroups.com.

[sage-devel] Re: Length of vectors in `plot_vector_field3d()`

[Eric Gourgoulhon]

Hi, 

There is no such length issue if you use vector fields on the Euclidean 
3-space, instead of plot_vector_field3d with a tuple of components. For 
instance:

sage: E. = EuclideanSpace()
sage: v1 = E.vector_field(1, 0, 0)
sage: v2 = E.vector_field(2, 0, 0)
sage: v1.plot()
sage: v2.plot()

yields 3d plots with arrows for v2 twice longer than those for v1, as you 
can check by running

sage: v1.plot() + v2.plot(color='red')

Note that the plot() method of vector fields has the optional argument 
"scale" to control the length of the arrows:

sage: v1.plot(scale=2)

yields the same plot as v2.plot()

Note also that the default coordinate range for the plot is (-8, 8). To use 
(-2, 2) as in your example, run

sage: v1.plot(max_range=2, scale=0.5) 

which is a shortcut for 

sage: v1.plot(ranges={x: (-2, 2), y: (-2, 2), z: (-2, 2)}, scale=0.5)

More details on 
https://doc.sagemath.org/html/en/reference/manifolds/sage/manifolds/differentiable/vectorfield.html#sage.manifolds.differentiable.vectorfield.VectorField.plot

Side remark: plots of vector fields are much faster with Sage 9.6 than with 
previous versions. 

Best wishes,

Eric.

Le dimanche 19 juin 2022 à 12:26:55 UTC+2, niran...@gmail.com a écrit :

> Dear all,
> I tried to plot constant vector fields.
> plot_vector_field3d((1,0,0), (x,-2,2), (y,-2,2), (z,-2,2))
> and
> plot_vector_field3d((2,0,0), (x,-2,2), (y,-2,2), (z,-2,2))
> Length of the arrows of first one are equal to the second one. I 
> expect that the length of arrows in second to be double that of the first. 
> Also their lengths are not equal to their magnitudes.
> Is it a bug? If it is the normal behavior, then any work around to 
> have length of the arrows to be equal to that of the magnitudes of the 
> vectors in the field.
>
> PS : The following shows vectors in the filed have their lengths equal to 
> their magnitudes. As expected.
> plot_vector_field3d((x,0,0), (x,-2,2), (y,-2,2), (z,-2,2))
>
> With regards
> Niranjana
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/64404d81-fa00-4853-a81d-b499b1e7b31cn%40googlegroups.com.

[sage-devel] Re: Let's update https://www.sagemath.org/help-video.html

[Eric Gourgoulhon]

Hi Matthias, 

Le samedi 4 juin 2022 à 06:18:55 UTC+2, Matthias Koeppe a écrit :

> Videos from this week's Sage days are available at 
> https://researchseminars.org/seminar/SageDays112358
>

Thanks!
 

> if some of you happen to have video recordings, in particular for 
> tutorial-like material, it would be great if you could make it available.


There is a series of very nice tutorial videos about manifolds in Sage by 
Christian Bär:
https://www.youtube.com/playlist?list=PLnrOCYZpQUuJlnQbQ48zgGk-Ks1t145Yw

There is also a video of some basic introduction to Sage (no manifolds!) 
that I've given on last March :
https://www.canal-u.tv/chaines/groupecalcul/sagemath
However, it is in French, being targeted to a French-speaking audience. 
The notebook on which it is based is in English though:
https://nbviewer.org/github/egourgoulhon/SageMathTour/blob/master/Notebooks/first_contact.ipynb
The video also presents some of the following notebooks:
https://github.com/egourgoulhon/SageMathTour/blob/master/README.md

Best wishes,

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/25be1084-bea6-4218-adce-10ac315675f8n%40googlegroups.com.

[sage-devel] Re: Help --> Sage Tutorial, Reference etc doesn't load in JupyterLab

[Eric Gourgoulhon]

Thanks for the report. 
I confirm the bug with Sage 9.7.beta0 on Ubuntu 20.04. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/181ffbbd-1e1f-4f51-9158-7e234e7ec938n%40googlegroups.com.

[sage-devel] Re: Jupyterlab installation very slow in Sage 9.6

[Eric Gourgoulhon]

Le dimanche 22 mai 2022 à 22:23:35 UTC+2, Nils Bruin a écrit :

> The rebuild should go through make nowadays. If you do
> export MAKE="make -j8"
> I think it should use up to 8 parallel jobs
>

Thanks for the tip. It works! I've tested it when installing Jupyterlab in 
Sage 9.7.beta0.
There remains the first question: why does installing Jupyterlab trigger 
the recompilation of all Cython files in src/sage ?

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ca1a0d6a-ad67-4d03-b50a-824eb384d235n%40googlegroups.com.

[sage-devel] Jupyterlab installation very slow in Sage 9.6

[Eric Gourgoulhon]

Hi, 

In a newly installed Sage 9.6 from source, I've moved on to install 
Jupyterlab (since it's still an optional package, cf. 
https://groups.google.com/g/sage-devel/c/orUpb-YXIHk/) by running 
./sage -i jupyterlab_widgets
as advertised in 
https://trac.sagemath.org/wiki/ReleaseTours/sage-9.6#JupyterLab3.3
This triggered the recompilation of 531 Cython files in sage-lib on a 
single thread, which on my i7 computer takes about half an hour or so. 
Is this really necessary? (a priori I don't see the link between Jupyterlab 
and these 531 Cython files in src/sage). If yes, is there any possibility 
to speed up the process by running it on multiple threads?

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/32f970d5-d4fb-4859-92a1-33cd5847e838n%40googlegroups.com.

[sage-devel] Re: favorable mention of sage in popular youtube video

[Eric Gourgoulhon]

NIce!

Eric.

Le samedi 14 mai 2022 à 20:36:09 UTC+2, wst...@gmail.com a écrit :

> Hi,
>
> Tim Daly (of Axiom) just told me that there is a very nice use of Sage
> at around 7:30-10:30 of this youtube video about RSA
>
> https://www.youtube.com/watch?v=-ShwJqAalOk
>
> I think it's being used on Windows, so props to Sage-on-windows.
>
> -- 
> William (http://wstein.org)
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/899f2fca-8ccc-494c-9b03-3d79dbb39420n%40googlegroups.com.

Re: [sage-devel] Question about factories, representations and multiple classes

[Eric Gourgoulhon]

Hi, 

Le samedi 14 mai 2022 à 00:07:02 UTC+2, David Roe a écrit :

> I think the following should work:
>
> class MyObject:
> def __classcall__(cls, arg):
>  if isinstance(arg, special):
>  return typecall(MyObject_specific_case, arg)
>  else:
>  return typecall(MyObject, arg)
>
> plus the same __init__ you had before.  I haven't checked it though
> David
>   
>

An alternative is to use __classcall_private__
For an example, see the class EuclideanSpace in
src/sage/manifolds/differentiable/examples/euclidean.py 


EuclideanSpace(n) actually returns an instance of the subclass 
EuclideanPlane if n = 2 or of the subclass Euclidean3dimSpace if n = 3.

Best wishes,

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/39214e36-80fa-4a33-988a-852b1a225773n%40googlegroups.com.

[sage-devel] Re: Sage Dev Prizes

[Eric Gourgoulhon]

Hi William,

Le dimanche 1 mai 2022 à 19:24:54 UTC+2, wst...@gmail.com a écrit :

> Hello Sage-Devel, 
>
> The 3 people who expressed interest in being on the Sage dev prize 
> committee are me, John Cremona, and Karl-Dieter Crisman. Would 
> anybody else like to be on the committee? 


Sorry for the delay in replying. I volunteer to be part of that committee, 
if this is not too late. 

Best wishes,

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/326f5567-44f4-492f-ac55-c3bf4d82013dn%40googlegroups.com.

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

[Eric Gourgoulhon]

Hi,

First of all many thanks to all of you who are improving the installation 
instructions!

Le mardi 26 avril 2022 à 14:22:28 UTC+2, seb@gmail.com a écrit :

> several Linux distributions carry reasonably up to date binary Sage 
> installations (and these can be installed on various VMs, e.g. on Windows’ 
> WSL, ChromeOS’ Crostini, etc)
>
> For example current LinuxMint and WSL are both on Ubuntu 20.04 LTS which 
> gives you Sage 9.0 (as in the example I’ve mentioned above). To get Sage 
> 9.5 you need Ubuntu 22.04 (I guess not very widespread at the moment). My 
> point is the following: until we discontinued the binary tarballs, the 
> straight ahead way to a Sage installation for Ubuntu systems lead you to 
> the current release. This is broken, now.
>
To avoid repeating the same advice to people asking how to install Sage 9.5 
in Ubuntu in  a *simple* way, I've prepared the following page, which has 
been improved by Samuel Lelièvre: 
[1] https://sagemanifolds.obspm.fr/install_ubuntu.html
I've already got testimony of persons not familiar with bash commands (not 
speaking about building from source) who could succeed in installing Sage 
9.5 in Ubuntu 20.04 by following these simple instructions. Of course, this 
is somehow redundant with Sage's installation guide or README.md, but this 
provides the minimal required steps, without having to read the full 
installation guide. 

Maybe [1] could be moved from https://sagemanifolds.obspm.fr/ to a better 
accessible place, e.g. to Sage's wiki (legacy or Trac). In particular, at 
the moment, this page can only be ammended by sending a PR to 
https://github.com/sagemanifolds/WebSite.

It would be pretty easy to prepare a bash script executing all the commands 
listed in [1] and distribute that script from the download section of Sage 
home page. But I don't know if this is a good idea (security issues?)

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/769799ff-7267-4a66-98db-d787f614772cn%40googlegroups.com.

[sage-devel] Re: Error in documentation: location of `constants.py`

[Eric Gourgoulhon]

Hi, 

Thanks for spotting these errors in the documentation. Would you open a 
ticket to fix them?
See https://doc.sagemath.org/html/en/developer/trac.html

Best wishes,

Eric.

Le vendredi 25 mars 2022 à 13:12:28 UTC+1, adarsh.k...@gmail.com a écrit :

> Apart from this, the documentation is outdated in several other places 
> also. For example,  on the same website, for an example on free modules it 
> is mentioned that
> ```
> the following is from the 
> file SAGE_ROOT/sage/sage/modules/free_module_element.pyx
> ```
>
> However the same is actually now at
> ```
> SAGE_ROOT/src/sage/modules/free_module_element.pyx
> ```
>
> Also, while explaining the `_matrix_` method, an example is given as
>
> [image: Screenshot from 2022-03-25 17-37-40.png]
>
> However, this class is now at
> ```
> SAG_ROOT/src/sage/graphs/generic_graph.py
> ```
>
> [image: Screenshot from 2022-03-25 17-41-13.png]
>
> and I believe several other inconsistencies would be existing.
> On Friday, March 25, 2022 at 1:21:23 PM UTC+5:30 Adarsh Kishore wrote:
>
>> Hi everyone,
>> I am running Sage v9.6.beta4 on Ubuntu 20.04 LTS. I was going through the 
>> online documentation of Sage and I came across this line on 
>> https://doc.sagemath.org/html/en/developer/coding_in_python.html
>> ```
>> Here is an example of the _latex_ and _repr_ functions for the Pi class. 
>> It is from the file SAGE_ROOT/src/sage/functions/constants.py
>> ```
>> [image: Screenshot from 2022-03-25 11-54-44.png]
>>
>> However, there is no constants.py in the mentioned directory. Instead, I 
>> found it on my Sage in
>> ```
>> SAGE_ROOT/src/sage/symbolic/constants.py
>> ```
>>
>> [image: Screenshot from 2022-03-25 11-52-01.png]
>>
>> [image: Screenshot from 2022-03-25 11-53-58.png]
>>
>> I think the documentation should be updated to reflect this.
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/39ecd91d-81f1-4ce9-b932-a122d76de273n%40googlegroups.com.

Re: [sage-devel] Notebook for testing display

[Eric Gourgoulhon]

Le mercredi 23 mars 2022 à 17:32:13 UTC+1, raymond@gmail.com a écrit :

> 1) I had to do 
>
> pip install ipympl
> Would it be reasonable to do a try/except in the header?
>

Actually a dependency of jupyterlab_widgets to ipympl has been introduced 
in Sage 9.6.beta5, so that as soon as you run

sage -i jupyterlab_widgets 

ipympl will automatically be installed. 
If JupyterLab becomes a standard package in Sage (cf. the discussion at 
https://groups.google.com/g/sage-devel/c/orUpb-YXIHk/m/GIxiKN4eDQAJ), then 
even running the above command will not be necessary. 

> 2) I changed the 3D graphs and animation to include
>
> 3) I changed/added @interact demos to allow external access to internal 
> values externally.  
>
As the notebook lies in some github repository,  feel free to submit a pull 
request to amend it. 
 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bfac52b6-1e38-4bb9-8624-8f11be09d7c6n%40googlegroups.com.

[sage-devel] Re: Proposal: make Jupyterlab a standard package

[Eric Gourgoulhon]

Le mercredi 23 mars 2022 à 12:01:15 UTC+1, kcrisman a écrit :

> Sorry for a tangential question - the overview page seems to imply that 
> *everything* from a (current) Jupyter notebook will work in a Jupyterlab 
> instance (and, by extension, presumably can easily be imported).  Would 
> that include the widgets we use for @interact?


As far as I can tell, all widgets work in Jupyterlab with Sage 9.6.beta5. 
In particular @interact works well. The widgets have been tested via this 
notebook: 
https://nbviewer.org/github/egourgoulhon/SageMathTest/blob/master/Notebooks/test_display.ipynb

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0ac8ac84-1961-4bd4-bb1c-92a3919fd0e3n%40googlegroups.com.

[sage-devel] Proposal: make Jupyterlab a standard package

[Eric Gourgoulhon]

Hi,

The optional package Jupyterlab has been upgraded to version 3.3.1 in 
https://trac.sagemath.org/ticket/32069
(merged in Sage 9.6.beta5)

Jupyterlab offers more functionalities than the classic Jupyter Notebook 
and is aimed to replace it, see e.g.
https://jupyterlab.readthedocs.io/en/stable/getting_started/overview.html

Maybe it is time to make it a standard package in Sage. 

To be clear, this is not to switch (yet) the default notebook interface 
from the  classic Jupyter Notebook to Jupyterlab, but simply to make the 
following commands work out of the box:

(1) sage -n   
(2) sage -n jupyterlab

with (1) launching the classic Jupyter Notebook (current behavior).
At the moment, (2) fails by complaining that Jupyterlab is not installed. 

In a second stage, we could get rid of the Jupyter Notebook as a standard 
package, but still keeping the same user interface as (1) and (2)  thanks 
to the extension nbclassic of Jupyterlab. This extension has been added to 
#32069. Then (1) will run Jupyterlab with the nbclassic interface, which is 
identical to the classic Jupyter Notebook one. 

In a third stage, we could make Jupyterlab the default by having (1) 
running it and having the old interface still accessible via

(3) sage -n nbclassic

Please vote. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/03958814-6538-476d-b13a-d6acd7d23c46n%40googlegroups.com.

[sage-devel] Re: spherical harmonics still broken in 9.5.beta8

[Eric Gourgoulhon]

Hi, 

The branch of the ticket https://trac.sagemath.org/ticket/33117 has been 
merged in Sage 9.6.beta5, so in Sage 9.6 spherical harmonics will agree 
with those of SymPy, SciPy, Mathematica and Wikipedia, and will have 
correct derivatives. There remains the issue of simplifying some 
sqrt(sin(theta)^2) terms which appear for odd orders m. This is now 
https://trac.sagemath.org/ticket/33501.

Eric.


Le mercredi 5 janvier 2022 à 09:14:23 UTC+1, Eric Gourgoulhon a écrit :

> Le mercredi 5 janvier 2022 à 08:27:56 UTC+1, Eric Gourgoulhon a écrit :
>
>>
>> Actually, the difference between the two results is essentially due to a 
>> different convention in the Condon-Shortley phase
>> (cf. 
>> https://en.wikipedia.org/wiki/Spherical_harmonics#Condon%E2%80%93Shortley_phase
>> ),
>> which makes Sage's spherical harmonics Y_l^m differ from Wikipedia and 
>> Mathematica ones by a factor (-1)^m.
>> The other difference in the above example is a lack of simplification of 
>> sqrt(sin(theta)^2). 
>>
>> I would vote for including the Condon-Shortley phase in Sage's spherical 
>> harmonics, since this is standard in quantum mechanics and this would make 
>> Sage agree with Wikipedia and Mathematica. 
>>
>
> I've opened 
> https://trac.sagemath.org/ticket/33117
> for this. 
>
> In doing so,  I've noticed that current Sage's spherical harmonics 
> disagree with SymPy as well.  
> I've also found  a very serious bug in the computation of derivatives of 
> spherical harmonics (see the ticket for details). This has not been seen 
> earlier probably because before https://trac.sagemath.org/ticket/25034 
> (merged in Sage 9.3), spherical harmonics were basically not usable in 
> Sage. 
>
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3034012d-c5a8-4626-99a1-9944fc264234n%40googlegroups.com.

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

[Eric Gourgoulhon]

This is https://trac.sagemath.org/ticket/30661

A workaround is 
sage: %display unicode_art# actually anything but plain
sage: %lsmagic

Eric.

Le dimanche 13 mars 2022 à 10:57:50 UTC+1, vdelecroix a écrit :

> Dear all,
>
> The IPython magic %lsmagic is supposed to list the available
> magic functions. However, this does not seem to work within
> the sage interpreter
>
> $ sage -ipython
> [1]: %lsmagic
> Available line magics:
> %alias %alias_magic %autoawait ...
>
> But
>
> $ sage
> sage: %lsmagic
> 
>
> Any idea on what is going wrong?
>
> Vincent
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0c64ffc3-3092-4714-9f3c-7a27dff08f9an%40googlegroups.com.

[sage-devel] Re: Wrong output of method arguments() on symbolic functions

[Eric Gourgoulhon]

Le mercredi 9 mars 2022 à 07:19:06 UTC+1, Matthias Koeppe a écrit :

> Note also that function('f')(y, x) does not actually create a function 
> with named arguments. 
> It is an ordinary symbolic expression that evaluates the undefined 
> function f of unspecified arity.
> Unbound variables in ordinary symbolic expression use alphabetical order. 
> https://trac.sagemath.org/ticket/32227 attempts to deprecate calling 
> "arguments" on such expressions.
>

This would indeed avoid some confusion; thanks for this ticket!

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bfd52f63-31e2-4f2b-ae57-4f42ea134b27n%40googlegroups.com.

[sage-devel] Wrong output of method arguments() on symbolic functions

[Eric Gourgoulhon]

Hi, 

We have currently

sage: x, y = var('x y')
sage: fyx = function('f')(y, x)
sage: fyx.arguments()
(x, y)

which is just the reverse of the expected output. 

Similarly, we have

sage: atan2(y,x).arguments()
(x, y)

Taking a look at the code, one sees that fyx.arguments() calls 
fyx.variables(), which returns a "sorted tuple of variables that occur in 
this expression" (according to the documentation). The "sorted" action 
explains the result. But the latter remains plain false. 

Note that SymPy provides the correct result:

sage: fyx._sympy_().args
(y, x)
sage: atan2(y,x)._sympy_().args
(y, x)

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/30ee081b-3337-42b8-b14e-f436b9f4d618n%40googlegroups.com.

[sage-devel] Re: documentation build complains about database Cremona (9.6.beta3)

[Eric Gourgoulhon]

Hi Vincent, 

I did not had such an issue on my Ubuntu 20.04 computer. Your log says

'cremona_mini.db' not found in any of 
['/home/debian/sage/local/share/cremona']

For some reason, this file is present in my sage root directory but not in 
yours:
ls -l /home/eric/sage/9.6-develop/local/share/cremona
total 8200
-rw-r--r-- 1 eric eric 8392704 févr.  8 14:34 cremona_mini.db

Best regards, 

Eric. 

Le mardi 1 mars 2022 à 08:25:26 UTC+1, vdelecroix a écrit :

> Dear all,
>
> On a Ubuntu 20.04, documentation builds stops with
>
> [sagemath_doc_html-none] [plotting ] File 
> "/home/debian/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/features/__init__.py",
>  
>
> line 559, in absolute_path
> [sagemath_doc_html-none] [plotting ] raise FeatureNotPresentError(self,
> [sagemath_doc_html-none] [plotting ] 
> sage.features.FeatureNotPresentError: database_cremona_mini_ellcurve is 
> not available.
> [sagemath_doc_html-none] [plotting ] 'cremona_mini.db' not found in any 
> of ['/home/debian/sage/local/share/cremona']
> [sagemath_doc_html-none] [plotting ] No equivalent system packages for 
> debian are known to Sage.
> [sagemath_doc_html-none] [plotting ] To install 
> database_cremona_mini_ellcurve using the Sage package manager, you can 
> try to run:
> [sagemath_doc_html-none] [plotting ] !sage -i database_cremona_ellcurve
> [sagemath_doc_html-none] [plotting ] No equivalent system packages for 
> pip are known to Sage.
> [sagemath_doc_html-none] [plotting ] Further installation instructions 
> might be available at https://github.com/JohnCremona/ecdata.
> [sagemath_doc_html-none] [plotting ] The inventory files are in 
> local/share/doc/sage/inventory/en/reference/plotting.
> [sagemath_doc_html-none] Error building the documentation.
>
> See also attached log. Any hint about what happened?
>
> Best
> Vincent
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c7666971-14e9-44d9-8dd0-745e1e6ba95bn%40googlegroups.com.

[sage-devel] Re: Sagemath in The Calabi-Yau Landscape

[Eric Gourgoulhon]

Hi,

Le samedi 26 février 2022 à 02:09:04 UTC+1, hohoa...@gmail.com a écrit :

> Dear List,
>
> Sagemath occupies a whole section (Appendix E) in "The Calabi-Yau 
> Landscape: from Geometry, to Physics, to Machine-Learning" by Yang-Hui He:
>
> https://arxiv.org/abs/1812.02893
>
> Does Sagemath Sagemanifolds have any tutorial on this kind of manifolds? 
>

Calabi-Yau manifolds as such have not been implemented in SageMath yet. 
Even generic complex manifolds are almost not developed, see 
https://trac.sagemath.org/ticket/18786
for an (old!) attempt. 
If someone is interested in implementing this, this would be a nice project!

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/042da679-8b91-4f17-adbb-182ebfca8d09n%40googlegroups.com.

[sage-devel] Re: sagemath 9.6 beta1 jupyter notebook missing output

[Eric Gourgoulhon]

Hi,

Le samedi 19 février 2022 à 03:28:03 UTC+1, hohoa...@gmail.com a écrit :

>
>
>1. In [3] only gives A^4 in Out [3] (missing A^0, A^1, A^2 and A^3)
>2.  In [4] gives no output (but In [8] does)
>3. In [6] gives no output (but In [7] does)
>
> There is no bug in all this. To display some item at each step of a loop 
use show() or print(), e.g.

for i in [0, 1, 2, 3, 4]:
 show(A^i)

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d7e99a7e-0c7a-4f03-8ee0-bbe373c746b4n%40googlegroups.com.

[sage-devel] Re: minimal requirements

[Eric Gourgoulhon]

Le vendredi 4 février 2022 à 01:05:05 UTC+1, Matthias Koeppe a écrit :

> And 
> https://doc.sagemath.org/html/en/reference/spkg/_prereq.html#spkg-prereq 
> has formatted versions of this information.
>
>
Shouldn't gfortran be added to the above lists (at least for Linux 
systems)? Of course, it is not strictly necessary, given that Sage can 
build its own. However,  since we are requiring system g++, it would make 
sense to demand system gfortran as well. In addition, this makes the build 
faster. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4504f67c-bad0-4bcc-a1a1-45bd987d4c27n%40googlegroups.com.

[sage-devel] Re: sage 9.5 build failed at package numpy-1.21.4 (on Windows Server 2019 WSL)

[Eric Gourgoulhon]

Hi, 

Have you followed the instructions in the section "Ubuntu on Windows 
Subsystem for Linux (WSL) prerequisite installation" of 
https://doc.sagemath.org/html/en/installation/source.html ?

Eric. 
Le jeudi 3 février 2022 à 10:22:11 UTC+1, hohoa...@gmail.com a écrit :

> Greetings,
>
> The instructions at  https://sagemanifolds.obspm.fr/install_ubuntu.html 
> were followed.
>
> It is much appreciated if someone would kindly point out what was missing 
> in the build process.
>
> Please find attached 'install.log.7z' and 'numpy-1.21.4.log.7z'
>
> Regards,
>
> phiho
>
> P.S: 
> $ uname -a
> Linux 4.4.0-17763-Microsoft #2268-Microsoft Thu Oct 07 16:36:00 PST 2021 
> x86_64 x86_64 x86_64 GNU/Linux
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8c6343cd-ba41-47f3-98df-9d09937caee5n%40googlegroups.com.

[sage-devel] Re: pdf docs from jupyter notebook

[Eric Gourgoulhon]

Hi, 

I am not sure to understand what your problem is:  from a Sage Jupyter 
notebook, if I click on the "Help" menu and select "Sage Documentation", 
then a new tab opens in the browser at the address
http://localhost:/kernelspecs/sagemath/doc/index.html
It displays html documentation and there is no attempt to show any pdf file.
This is with Sage 9.5.rc0 running on Ubuntu 20.04. 

Eric.
Le dimanche 9 janvier 2022 à 19:26:01 UTC+1, Steven Trogdon a écrit :

> From a new Sagemath jupyter notebook if I select the Sage Documentation I 
> have numerous PDF links which are broken., for example
>
> [W 11:01:19.061 NotebookApp] 404 GET 
> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1): Kernel spec pdf not 
> found
> [W 11:01:19.062 NotebookApp] 404 GET 
> /kernelspecs/pdf/en/tutorial/SageTutorial.pdf (::1) 3.14ms referer=
> http://localhost:/kernelspecs/sagemath/doc/index.html
>
> Are these links supposed to work from the notebook? They do work if the 
> path
>
> file:///$SAGE_ROOT/local/share/doc/sage/html/en/index.html
>
> is pasted in a brower.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4b6e5dbd-0e5f-4bc5-a2dc-cbc56c7440bcn%40googlegroups.com.

Re: [sage-devel] Re: spherical harmonics still broken in 9.5.beta8

[Eric Gourgoulhon]

Le jeudi 6 janvier 2022 à 06:20:28 UTC+1, Jonathan Thornburg a écrit :

> I think this problem is worse than "just" a lack of simplification: 
> if sin(theta) < 0 then sqrt(sin(theta)^2 != sin(theta), i.e., the 
> theta dependence is wrong, not "just" not-fully-simplified. 
>
>
Well, the standard spherical coordinate theta (the colatitude on S^2) lies 
in [0, pi], so that sin(theta) >= 0. 
This simplification issue should be dealt either in 
https://trac.sagemath.org/ticket/33117 (since it seems pretty easy to 
implement),  or in a follow up ticket.

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/261963d4-32c8-4316-aff8-67b66f0c79een%40googlegroups.com.

[sage-devel] Re: spherical harmonics still broken in 9.5.beta8

[Eric Gourgoulhon]

Le mercredi 5 janvier 2022 à 08:27:56 UTC+1, Eric Gourgoulhon a écrit :

>
> Actually, the difference between the two results is essentially due to a 
> different convention in the Condon-Shortley phase
> (cf. 
> https://en.wikipedia.org/wiki/Spherical_harmonics#Condon%E2%80%93Shortley_phase
> ),
> which makes Sage's spherical harmonics Y_l^m differ from Wikipedia and 
> Mathematica ones by a factor (-1)^m.
> The other difference in the above example is a lack of simplification of 
> sqrt(sin(theta)^2). 
>
> I would vote for including the Condon-Shortley phase in Sage's spherical 
> harmonics, since this is standard in quantum mechanics and this would make 
> Sage agree with Wikipedia and Mathematica. 
>

I've opened 
https://trac.sagemath.org/ticket/33117
for this. 

In doing so,  I've noticed that current Sage's spherical harmonics disagree 
with SymPy as well.  
I've also found  a very serious bug in the computation of derivatives of 
spherical harmonics (see the ticket for details). This has not been seen 
earlier probably because before https://trac.sagemath.org/ticket/25034 
(merged in Sage 9.3), spherical harmonics were basically not usable in 
Sage. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3772782b-8f69-4904-9770-ceb427249414n%40googlegroups.com.

[sage-devel] Re: spherical harmonics still broken in 9.5.beta8

[Eric Gourgoulhon]

Hi,

Le mercredi 5 janvier 2022 à 00:36:11 UTC+1, Jonathan Thornburg a écrit :

> Sage has long had problems with spherical harmonics, e.g., this thread 
> from June 2019: 
> https://groups.google.com/g/sage-support/c/I_d_meMxRbM/m/Esxo5UO2BAAJ 
>
> As of 9.5.beta8, spherical harmonics are (still) broken for some 
> arguments, 
> with the test case noted in that earlier thread still giving the same 
> (wrong) result: 
> sage: theta,phi = var('theta,phi') 
> sage: spherical_harmonic(1,1,theta,phi) 
> 1/4*sqrt(3)*sqrt(2)*sqrt(sin(theta)^2)*e^(I*phi)/sqrt(pi) 
> The correct result would be 
> -1/4*sqrt(6)*e^(I*phi)*sin(theta)/sqrt(pi) 
> (see, e.g., https://en.wikipedia.org/wiki/Table_of_spherical_harmonics). 
>
>  
Actually, the difference between the two results is essentially due to a 
different convention in the Condon-Shortley phase
(cf. 
https://en.wikipedia.org/wiki/Spherical_harmonics#Condon%E2%80%93Shortley_phase),
which makes Sage's spherical harmonics Y_l^m differ from Wikipedia and 
Mathematica ones by a factor (-1)^m.
The other difference in the above example is a lack of simplification of 
sqrt(sin(theta)^2). 

I would vote for including the Condon-Shortley phase in Sage's spherical 
harmonics, since this is standard in quantum mechanics and this would make 
Sage agree with Wikipedia and Mathematica. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b7f40005-d3f0-4289-a51d-7b7c216c85fen%40googlegroups.com.

[sage-devel] Re: \Bold command definition in every LaTeX output

[Eric Gourgoulhon]

Le jeudi 23 décembre 2021 à 03:16:13 UTC+1, John H Palmieri a écrit :

> Sure, that sounds like a good idea.
>
>
In the above example, I used LatexExpr  as a place holder for 
_bold_command, but maybe there is a better way (at least, LatexExpr has the 
advantage to not require any new injection in the global namespace).

Eric.
 

> - John
>
> On Wednesday, December 22, 2021 at 3:05:44 AM UTC-8 Eric Gourgoulhon wrote:
>
>> Le mercredi 22 décembre 2021 à 00:26:58 UTC+1, John H Palmieri a écrit :
>>
>>> I have no objection to this, but the purpose for using \Bold{...} was to 
>>> make its behavior easily customizable, since some people might want 
>>> \mathbf{...} and some might want \mathbb{...}. 
>>>
>>
>> The customization could be performed at the Python level, instead of the 
>> LaTeX one, e.g.  something like:
>>
>> def _latex_(self):
>> return LatexExpr.bold_command() + r"{Q}"
>>
>> with bold_command() being a static method of LatexExpr that returns the 
>> class attribute _bold_command. The latter would be initialized to 
>> r"\mathbf" and could be customized by the end user thanks to some 
>> static/class method of LatexExpr, e.g. 
>>
>> sage: LatexExpr.set_bold_command("mathbb")
>>
>> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1f9a5ff7-11f0-4cc5-a7c8-bf0bb0521382n%40googlegroups.com.

[sage-devel] Re: \Bold command definition in every LaTeX output

[Eric Gourgoulhon]

Le mercredi 22 décembre 2021 à 00:26:58 UTC+1, John H Palmieri a écrit :

> I have no objection to this, but the purpose for using \Bold{...} was to 
> make its behavior easily customizable, since some people might want 
> \mathbf{...} and some might want \mathbb{...}. 
>

The customization could be performed at the Python level, instead of the 
LaTeX one, e.g.  something like:

def _latex_(self):
return LatexExpr.bold_command() + r"{Q}"

with bold_command() being a static method of LatexExpr that returns the 
class attribute _bold_command. The latter would be initialized to 
r"\mathbf" and could be customized by the end user thanks to some 
static/class method of LatexExpr, e.g. 

sage: LatexExpr.set_bold_command("mathbb")

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7000414b-6437-46af-9061-c03087c9f976n%40googlegroups.com.

[sage-devel] Re: \Bold command definition in every LaTeX output

[Eric Gourgoulhon]

Hi,

Le lundi 20 décembre 2021 à 12:06:05 UTC+1, AlbertHilb a écrit :

> Problem solved! Thank you very much!
>

That being said, it seems to me that these \newcommand{Bold} in each LaTeX 
output (!) are  an unnecessary pollution of  the Jupyter notebooks in 
%display latex mode. Unless there might be a reason for it, why not 
replacing lines like
return r"\Bold{Q}"
by
return r"\mathbf{Q}"
in the relevant  _latex_ methods ? (the above example is line 279 of 
src/sage/rings/rational_field.py) 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d56a3258-a95e-49b4-beb8-b38ed7493014n%40googlegroups.com.

[sage-devel] Re: Sage 9.5.beta8: ipython help triggers pythran deprecation warnings

[Eric Gourgoulhon]

More precisely, these are deprecation warnings from numpy functions invoked 
by pythran.

Le lundi 13 décembre 2021 à 22:56:03 UTC+1, Eric Gourgoulhon a écrit :

> Hi,
>
> In the just released Sage 9.5.beta8, invoking help on a function with the 
> question mark yields a bunch of pythran deprecation warnings before the 
> help shows off:
>
> sage: sin?
> /home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4520:
>  
> DeprecationWarning: `np.bool` is a deprecated alias for the builtin `bool`. 
> To silence this warning, use `bool` by itself. Doing this will not modify 
> any behavior and is safe. If you specifically wanted the numpy scalar type, 
> use `np.bool_` here.
> Deprecated in NumPy 1.20; for more details and guidance: 
> https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
>   if not hasattr(numpy, method):
> /home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4520:
>  
> DeprecationWarning: `np.complex` is a deprecated alias for the builtin 
> `complex`. To silence this warning, use `complex` by itself. Doing this 
> will not modify any behavior and is safe. If you specifically wanted the 
> numpy scalar type, use `np.complex128` here.
> Deprecated in NumPy 1.20; for more details and guidance: 
> https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
>   if not hasattr(numpy, method):
> /home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4520:
>  
> DeprecationWarning: `np.float` is a deprecated alias for the builtin 
> `float`. To silence this warning, use `float` by itself. Doing this will 
> not modify any behavior and is safe. If you specifically wanted the numpy 
> scalar type, use `np.float64` here.
> Deprecated in NumPy 1.20; for more details and guidance: 
> https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
>   if not hasattr(numpy, method):
> /home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4553:
>  
> DeprecationWarning: `np.bool` is a deprecated alias for the builtin `bool`. 
> To silence this warning, use `bool` by itself. Doing this will not modify 
> any behavior and is safe. If you specifically wanted the numpy scalar type, 
> use `np.bool_` here.
> Deprecated in NumPy 1.20; for more details and guidance: 
> https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
>   obj = getattr(themodule, elem)
> /home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4553:
>  
> DeprecationWarning: `np.complex` is a deprecated alias for the builtin 
> `complex`. To silence this warning, use `complex` by itself. Doing this 
> will not modify any behavior and is safe. If you specifically wanted the 
> numpy scalar type, use `np.complex128` here.
> Deprecated in NumPy 1.20; for more details and guidance: 
> https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
>   obj = getattr(themodule, elem)
> /home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4553:
>  
> DeprecationWarning: `np.float` is a deprecated alias for the builtin 
> `float`. To silence this warning, use `float` by itself. Doing this will 
> not modify any behavior and is safe. If you specifically wanted the numpy 
> scalar type, use `np.float64` here.
> Deprecated in NumPy 1.20; for more details and guidance: 
> https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
>   obj = getattr(themodule, elem)
>
> It seems that pythran has just been added in this release. 
>
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8b6224b4-89e9-4969-9ea3-deaf90b58cddn%40googlegroups.com.

[sage-devel] Sage 9.5.beta8: ipython help triggers pythran deprecation warnings

[Eric Gourgoulhon]

Hi,

In the just released Sage 9.5.beta8, invoking help on a function with the 
question mark yields a bunch of pythran deprecation warnings before the 
help shows off:

sage: sin?
/home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4520:
 
DeprecationWarning: `np.bool` is a deprecated alias for the builtin `bool`. 
To silence this warning, use `bool` by itself. Doing this will not modify 
any behavior and is safe. If you specifically wanted the numpy scalar type, 
use `np.bool_` here.
Deprecated in NumPy 1.20; for more details and guidance: 
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  if not hasattr(numpy, method):
/home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4520:
 
DeprecationWarning: `np.complex` is a deprecated alias for the builtin 
`complex`. To silence this warning, use `complex` by itself. Doing this 
will not modify any behavior and is safe. If you specifically wanted the 
numpy scalar type, use `np.complex128` here.
Deprecated in NumPy 1.20; for more details and guidance: 
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  if not hasattr(numpy, method):
/home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4520:
 
DeprecationWarning: `np.float` is a deprecated alias for the builtin 
`float`. To silence this warning, use `float` by itself. Doing this will 
not modify any behavior and is safe. If you specifically wanted the numpy 
scalar type, use `np.float64` here.
Deprecated in NumPy 1.20; for more details and guidance: 
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  if not hasattr(numpy, method):
/home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4553:
 
DeprecationWarning: `np.bool` is a deprecated alias for the builtin `bool`. 
To silence this warning, use `bool` by itself. Doing this will not modify 
any behavior and is safe. If you specifically wanted the numpy scalar type, 
use `np.bool_` here.
Deprecated in NumPy 1.20; for more details and guidance: 
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  obj = getattr(themodule, elem)
/home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4553:
 
DeprecationWarning: `np.complex` is a deprecated alias for the builtin 
`complex`. To silence this warning, use `complex` by itself. Doing this 
will not modify any behavior and is safe. If you specifically wanted the 
numpy scalar type, use `np.complex128` here.
Deprecated in NumPy 1.20; for more details and guidance: 
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  obj = getattr(themodule, elem)
/home/eric/sage/9.5.develop/local/lib/python3.8/site-packages/pythran/tables.py:4553:
 
DeprecationWarning: `np.float` is a deprecated alias for the builtin 
`float`. To silence this warning, use `float` by itself. Doing this will 
not modify any behavior and is safe. If you specifically wanted the numpy 
scalar type, use `np.float64` here.
Deprecated in NumPy 1.20; for more details and guidance: 
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  obj = getattr(themodule, elem)

It seems that pythran has just been added in this release. 

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d4278f9b-e559-4180-8374-446c05120182n%40googlegroups.com.

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

[Eric Gourgoulhon]

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 :

> If I running 3 lines codes below:
>
> PR. = PolynomialRing(Zmod(0x10001))
> f = (x + y) ^ 3
> print(f.factor())
>
> sagemath will crash:
>  
> Unhandled SIGSEGV: A segmentation fault occurred. This probably occurred 
> because a *compiled* module has a bug in it and is not properly wrapped 
> with sig_on(), sig_off(). Python will now terminate. 
>  
> /opt/sagemath-9.2/src/bin/sage-python: line 2: 1044 Segmentation fault 
> (core dumped) sage -python "$@"
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a6d546f4-0799-4bb3-983d-b48fc3fe92afn%40googlegroups.com.

Re: [sage-devel] Docker images no longer being build and is gitlab still maintained?

[Eric Gourgoulhon]

Hi, 

Le vendredi 3 décembre 2021 à 05:06:30 UTC+1, maarten...@navara.nl a écrit :

> In the meantime I managed to verify that aside from the gitlab CI/CD there 
> are no other things that are broken. Meaning that I managed to build the 
> docker file shipped with sage just fine on my laptop. I pushed a build of 
> 9.4 to https://hub.docker.com/r/mderickx/sagemath/ in case anyone is 
> interested.
>

Thanks for the 9.4 image! 
I've tried it to run a notebook with Binder, by inserting 
FROM mderickx/sagemath:latest
in the Dockerfile of the repository
https://github.com/egourgoulhon/SageMathTour
But it fails, as the previous Sage images (cf. the discussion at 
https://groups.google.com/g/sage-devel/c/GCOg8oT3beI/m/I_hWqTYaAQAJ), with 
the following error:

2021-12-03T10:30:51Z [Normal] Successfully pulled image 
"gcr.io/binderhub-288415/r2d-staging-g5b5b759-egourgoulhon-2dsagemathtour-2fda44:32fab2e884998806d7465f08b7dc21a8a99793d8"
 
in 49.782009677s
2021-12-03T10:30:52Z [Normal] Created container notebook
2021-12-03T10:30:52Z [Normal] Started container notebook
Spawn failed: Timeout
Launch attempt 2 failed, retrying...
Server requested
2021-12-03T10:35:09.007721Z [Normal] Successfully assigned 
prod/jupyter-egourgoulhon-2dsagemathtour-2dyl7nva8s to 
gke-prod-user-202009-b9c03ca0-5ga5
2021-12-03T10:35:10Z [Normal] Container image 
"jupyterhub/mybinder.org-tc-init:2020.12.4-n655.hfe65496" already present 
on machine
2021-12-03T10:35:10Z [Normal] Created container tc-init
2021-12-03T10:35:10Z [Normal] Started container tc-init
2021-12-03T10:35:11Z [Normal] Pulling image 
"gcr.io/binderhub-288415/r2d-staging-g5b5b759-egourgoulhon-2dsagemathtour-2fda44:32fab2e884998806d7465f08b7dc21a8a99793d8"
2021-12-03T10:36:58Z [Normal] Successfully pulled image 
"gcr.io/binderhub-288415/r2d-staging-g5b5b759-egourgoulhon-2dsagemathtour-2fda44:32fab2e884998806d7465f08b7dc21a8a99793d8"
 
in 1m47.176651527s
2021-12-03T10:37:00Z [Normal] Created container notebook
2021-12-03T10:37:00Z [Normal] Started container notebook
Failed to connect to event stream

More precisely, this was obtained by clicking on the button "Execute on 
Binder" of 
https://nbviewer.org/github/egourgoulhon/SageMathTour/blob/master/Notebooks/demo_pseudo_Riemannian_Schwarzschild.ipynb

Again, this used to work with the Sage 9.3.beta8 image and previous ones at 
some time. So it could be that a change has been performed on the Binder 
side...

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9f422d44-39a5-47ea-8cd3-0d06ec80c9b9n%40googlegroups.com.

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

[Eric Gourgoulhon]

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 with my internet connection. Am I the only one 
> experiencing this?
>
> 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/421fa312-9885-48a1-bc10-d6031c7933acn%40googlegroups.com.

[sage-devel] trac server very slow to respond

[Eric Gourgoulhon]

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 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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1916744f-e136-4b1a-a4d3-c065cf829395n%40googlegroups.com.

[sage-devel] New videos on manifolds in Sage

[Eric Gourgoulhon]

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 
Maybe another link could be added to
https://www.sagemath.org/help-video.html ?

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e6425aa3-a728-4840-96ab-31ed41cadf54n%40googlegroups.com.

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

[Eric Gourgoulhon]

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 with how openblas was 
>> built. You probably have to use a sage-9.2 docker container, or wait 
>> for sage 9.5 to come out. 
>>
>> Thanks for your feedback. However, I am not sure this is the source of 
> the issue here, because the Sage 9.3.beta8 Docker image used to work on 
> Binder, until quite recently. So maybe there has been some change on the 
> Binder side. I should try with Sage 9.2 though...
>

Well, there is no need to test further against the Sage version since the 
user who reported the issue on ask.sagemath is using Sage 9.1:
https://github.com/calculuslab/Calculus_Lab/blob/main/Dockerfile

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 discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/98ee36b1-8ae4-40db-9c00-6c8e0e649ec9n%40googlegroups.com.