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

Dear all, First I thank you all for Sage-9.6 release. I tried JupyterLab in Sage 9.6 on Gentoo x86_64. Looks cool. But I noticed that in Help section, if I click on Sage Tutorial or Reference etc, the page is not loading. It shows up a blank tab and continuously tries to load but shows n

[sage-devel] [ 1 = 1+0i ] <=> [ 1 = 1 ]

Dear All, Is this feasible [ 1 = 1+0i ] <=> [ 1 = 1 ] ? Regards, phiho ** if [ 1 = 1+0i ]; then # Make sure that SAGE_ROOT is either an absolute physical directory name # or empty. *# An absolute physical directory name has already been embedded and exported* *# at configuration ti

[sage-devel] Re: The path MUST NOT contain spaces.

On Tuesday, May 24, 2022 at 3:11:00 PM UTC-7 hohoa...@gmail.com wrote: > Does this apply only to "$SAGE_ROOT"? > Can sub-directories of "$SAGE_ROOT" (like "lo space cal") contain spaces? > Is it OK for $SAGE_LOCAL to contain spaces? If it is so, why the > differences? > We do not systematically

[sage-devel] The path MUST NOT contain spaces.

Dear All, Does this apply only to "$SAGE_ROOT"? Can sub-directories of "$SAGE_ROOT" (like "lo space cal") contain spaces? Is it OK for $SAGE_LOCAL to contain spaces? If it is so, why the differences? Thank you for your help. Regards, phiho ** if contains_spaces X${SAGE_ROOT}X ; then ech

Re: [sage-devel] $SAGE_ROOT/src/MANIFEST.in

Hi, > > What does it mean for 'MANIFEST.in' to 'include' 'MANIFEST.in'? > See https://packaging.python.org/en/latest/guides/using-manifest-in/ > This is not specific to Sage. This is very interesting. Thanks so much. phiho On Tue, May 24, 2022 at 2:11 PM ph h wrote: > Dear All, > > How do t

[sage-devel] assumptions and solve

Dear All, is this a known "feature"? ``` sage: var('t'); sage: with assuming(t>-1): : solve(t+2<0,t) [[t < -2]] # I expected [] ``` Thanks S. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop rece

[sage-devel] Re: load deprecation warning in SageCell

Fixed in https://trac.sagemath.org/ticket/33771 On Tuesday, May 24, 2022 at 11:10:13 AM UTC-7 ingo...@gmail.com wrote: > When I call > *load('https://raw.githubusercontent.com/ingodahn/sageutils/master/physics.py > ')* > in

[sage-devel] Re: $SAGE_ROOT/src/MANIFEST.in

See https://packaging.python.org/en/latest/guides/using-manifest-in/ This is not specific to Sage. On Tuesday, May 24, 2022 at 11:11:52 AM UTC-7 hohoa...@gmail.com wrote: > Dear All, > > How do these 'include' statements in 'MANIFEST.in' work? > What does it mean for 'MANIFEST.in' to 'include'

[sage-devel] $SAGE_ROOT/src/MANIFEST.in

Dear All, How do these 'include' statements in 'MANIFEST.in' work? What does it mean for 'MANIFEST.in' to 'include' 'MANIFEST.in'? Is there a corresponding 'MANIFEST' generated from this 'MANIFEST.in' ? Thank you for your help. Regards, phiho global-include *.c *.cc *.cpp *.h *.hh *.hpp *.

[sage-devel] load deprecation warning in SageCell

When I call *load('https://raw.githubusercontent.com/ingodahn/sageutils/master/physics.py ')* in a sagecell I get in the output */home/sc_serv/sage/local/var/lib/sage/venv-python3.10.3/lib/python3.10/site-packages/sage/misc/re

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

On Tue, May 24, 2022 at 11:07 AM Dima Pasechnik wrote: > > On Tue, May 24, 2022 at 10:04 AM Samuel Lelievre > wrote: > > > > Side note: if using `sage -i`, prepending `V=0` will > > suppress most of the build's verbosity. Example: > > ``` > > $ V=0 sage -i jupyterlab_widgets > > ``` > > > > I can

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

On Tue, May 24, 2022 at 10:04 AM Samuel Lelievre wrote: > > Side note: if using `sage -i`, prepending `V=0` will > suppress most of the build's verbosity. Example: > ``` > $ V=0 sage -i jupyterlab_widgets > ``` > > I cannot answer the following two questions: > > - why does installing JupyterLab a

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

Side note: if using `sage -i`, prepending `V=0` will suppress most of the build's verbosity. Example: ``` $ V=0 sage -i jupyterlab_widgets ``` I cannot answer the following two questions: - why does installing JupyterLab after building Sage trigger recompilation of all Cython files in src/sage?