[sage-support] Re: Does sagemath support something similar to numpy's einsum for symbolic arrays?

2024-04-15 Thread Matthias Koeppe
You might be looking 
for 
https://doc.sagemath.org/html/en/reference/tensor_free_modules/sage/tensor/modules/tensor_with_indices.html

On Tuesday, April 9, 2024 at 6:59:27 AM UTC-7 Anton Todorov wrote:

> Einsum: https://numpy.org/doc/stable/reference/generated/numpy.einsum.html
>
> It is a way to define multiple operations on arrays of arbitrary shape. 
> I've not seen anything that suggests this is implemented in sagemath, but I 
> was hoping there might be something hidden.
>
> What I need this for is to calculate symbolic results of array operations 
> which are too cumbersome to represent as matrix operations.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/9acdf077-64a3-4034-8835-e1d806e0e049n%40googlegroups.com.


[sage-support] Re: Is there a way to use Sage's Jupyter outside the sage shell ?

2024-04-15 Thread Matthias Koeppe
Yes, this is documented 
in 
https://doc.sagemath.org/html/en/installation/launching.html#setting-up-sagemath-as-a-jupyter-kernel-in-an-existing-jupyter-notebook-or-jupyterlab-installation



On Monday, April 8, 2024 at 11:16:45 AM UTC-7 Emmanuel Charpentier wrote:

> Setup : Sage 10.4.beta1 running on Ubuntu 22.04 LTS under WSL2 in Windows 
> 11 (don’t get me started…). I also installed emacs and its juyter 
>  package, which is able to use 
> Sage-installed kernels … when emacs is started from the Sage shell. [ Yes, 
> there is a point to this…]
>
> What I want to do is to be able to use these Sage-installed kernels from 
> outside the Sage shell environment, thus avoiding to duplicate the Sage 
> Jupyter installation. In other words, I want a jupyter command that is 
> able to finfd the Sage-instaled kernels in their correct environment.
>
> Is there any way to do that ?
> ​
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/e526ffb3-bebe-49af-9f1d-075b0aacff3an%40googlegroups.com.


Re: [sage-support] Errors building Sage 10.3 in Sonoma 14.3.1

2024-03-29 Thread Matthias Koeppe
This one is fixed in https://github.com/sagemath/sage/pull/37646



On Wednesday, March 27, 2024 at 9:58:10 AM UTC-7 Dima Pasechnik wrote:

> I've cut out the interesting part of the log.
> It's a linker error (IMHO the linking should be done with C++, not
> with C compiler, but that's probably OK on macOS).
> Related to GiNaC (not a surprise)
>
> Anyway, I haven't seen this sort of errors before. Something for Apple 
> fans...
>
>
> On Wed, Mar 27, 2024 at 3:54 PM Jon Higa  
> wrote:
> >
> > Switched to this, continuing in the same directory:
> >
> > git clean -xdf
> > source .homebrew-build-env
> > make configure
> > ./configure --prefix=/usr/local/sage/10.3 --enable-database_odlyzko_zeta 
> --disable-editable 
> --with-python=/opt/homebrew/opt/pyt...@3.11/bin/python3.11
> > make
> >
> > New logs attached.
> >
> > Thanks.
> >
> > On Wednesday, March 27, 2024 at 6:24:37 AM UTC-4 Dima Pasechnik wrote:
> >
> > sagemath doesn't officially support Python 3.12.
> > Can you try with 3.11 instead?
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "sage-support" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to sage-support...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/9bfc9093-a640-4c75-9b62-0fd21ab3474en%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/75342595-e9f9-4803-920f-601e422ef947n%40googlegroups.com.


Re: [sage-support] Sagemanifolds error in example notebook

2024-02-07 Thread Matthias Koeppe
On Wednesday, February 7, 2024 at 7:00:07 AM UTC-8 Eric Gourgoulhon wrote:

I don't know about any automated way to check that the example notebooks 
are up to date.


One can use "jupyter nbconvert --to notebook --execute" for this
https://nbconvert.readthedocs.io/en/latest/execute_api.html

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/6fc4764c-b4e9-439a-a359-97fd52372facn%40googlegroups.com.


[sage-support] Re: Developer's guide and configure : the list of packages needs some updating

2024-01-23 Thread Matthias Koeppe
By the way, a further improvement to this section in the installation guide 
is waiting for review in https://github.com/sagemath/sage/pull/37056

On Tuesday, January 23, 2024 at 10:13:08 AM UTC-8 Matthias Koeppe wrote:

> Many of these packages appeared in the 10.2 developer's guide only because 
> of a bug in the script that generates this list.
>
> This is already fixed in the current beta; see 
> https://deploy-livedoc--sagemath.netlify.app/html/en/installation/source#debian-ubuntu-package-installation
>
> Nevertheless, the package names should be corrected in build/pkgs/ name>/distros/debian.txt, as Dima explained.
> They only affect the experimental configuration explained in 
> https://github.com/sagemath/sage/wiki/Sage-10.2-Release-Tour#configure---enable-system-site-packages-experimental
>  
> and are otherwise just documentation.
>
>
>
> On Monday, January 22, 2024 at 11:44:43 PM UTC-8 Emmanuel Charpentier 
> wrote:
>
>> For installation from source on Debian, a few packages have incorrect 
>> names in the Developer’s guide (and possibly in the configuration process 
>> files) :
>> | Replace | with | 
>> ++--| | 
>> beautifulsoup4 | python3-bs4 | | cython | cython3 | | hatch-vcs | 
>> python3-hatch-vcs | | importlib-resources | python3-importlib-resources | | 
>> ipykernel | python3-ipykernel | | meson-python | python3-mesonpy (?) | | 
>> python-fastjsonschema | python3-fastjsonschema | | 
>> python-hatch-fancy-pypi-readme | python3-hatch-fancy-pypi-readme | | 
>> python-tinycss2 | python3-tinycss2 | | rpy2 | python3-rpy2 | | 
>> setuptools-scm | python3-setuptools-scm | | sphinxcontrib-websupport | 
>> python3-sphinxcontrib.websupport | 
>>
>> A question : are clang and clang-relatedpackages necessary or a “simple 
>> recommendation” ? In the latter case, what is the rationale ?
>>
>> Another couple of questions :
>>
>>- 
>>
>>How to report such problems efficiently ?
>>- 
>>
>>What to fix in the source in order to fix them ?
>>
>> HTH,
>> ​
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/52dc6746-d826-4b3a-91da-cb1a3fc36af8n%40googlegroups.com.


[sage-support] Re: Developer's guide and configure : the list of packages needs some updating

2024-01-23 Thread Matthias Koeppe
Many of these packages appeared in the 10.2 developer's guide only because 
of a bug in the script that generates this list.

This is already fixed in the current beta; 
see 
https://deploy-livedoc--sagemath.netlify.app/html/en/installation/source#debian-ubuntu-package-installation

Nevertheless, the package names should be corrected in build/pkgs//distros/debian.txt, as Dima explained.
They only affect the experimental configuration explained 
in 
https://github.com/sagemath/sage/wiki/Sage-10.2-Release-Tour#configure---enable-system-site-packages-experimental
 
and are otherwise just documentation.



On Monday, January 22, 2024 at 11:44:43 PM UTC-8 Emmanuel Charpentier wrote:

> For installation from source on Debian, a few packages have incorrect 
> names in the Developer’s guide (and possibly in the configuration process 
> files) :
> | Replace | with | 
> ++--| | 
> beautifulsoup4 | python3-bs4 | | cython | cython3 | | hatch-vcs | 
> python3-hatch-vcs | | importlib-resources | python3-importlib-resources | | 
> ipykernel | python3-ipykernel | | meson-python | python3-mesonpy (?) | | 
> python-fastjsonschema | python3-fastjsonschema | | 
> python-hatch-fancy-pypi-readme | python3-hatch-fancy-pypi-readme | | 
> python-tinycss2 | python3-tinycss2 | | rpy2 | python3-rpy2 | | 
> setuptools-scm | python3-setuptools-scm | | sphinxcontrib-websupport | 
> python3-sphinxcontrib.websupport | 
>
> A question : are clang and clang-relatedpackages necessary or a “simple 
> recommendation” ? In the latter case, what is the rationale ?
>
> Another couple of questions :
>
>- 
>
>How to report such problems efficiently ?
>- 
>
>What to fix in the source in order to fix them ?
>
> HTH,
> ​
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/af485425-18b3-4c72-b54d-077dd3a85603n%40googlegroups.com.


Re: [sage-support] Sage Docker images are outdated: still on Sage 9.7

2023-06-19 Thread Matthias Koeppe
The page 
https://doc.sagemath.org/html/en/developer/portability_testing.html#using-our-pre-built-docker-images-for-development-in-vs-code
 
has a link to a number of more container options



On Monday, June 19, 2023 at 3:29:35 PM UTC-7 Beth Claire wrote:

> I saw the cocalc docker, and yeah, it's too big to run on my laptop.
>
> On Monday, June 19, 2023 at 5:07:54 PM UTC-4 William Stein wrote:
>
>> On Mon, Jun 19, 2023 at 1:19 PM William Stein  wrote: 
>> > 
>> > On Mon, Jun 19, 2023 at 11:58 AM Beth Claire <318...@gmail.com> wrote: 
>> > > 
>> > > The docker image available here: 
>> > > https://hub.docker.com/r/sagemath/sagemath 
>> > > Has not been updated since Sagemath 9.7. Is that image supported by 
>> the sage team? Is there another image I should use? 
>> > 
>> > I also build Docker images for x86_64 and aarch64 (apple silicon) for 
>> > cocalc-docker. These are more up to date and 
>> > instructions here: https://github.com/sagemathinc/cocalc-docker 
>>
>> I just checked and actually only sage-9.8 is in that image. I'm 
>> building a new sage-10.0 image today. 
>>
>> William 
>>
>> > 
>> > These are much bigger than the sagemath images since they include 
>> > julia, latex, and many other things, so they may or may 
>> > not be of interest to you. 
>> > 
>> > https://hub.docker.com/r/sagemathinc/cocalc/tags 
>>
>>
>>
>> -- 
>> William (http://wstein.org) 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/da2bbdef-0c8a-4cb0-96ad-8d742f47c3aen%40googlegroups.com.


[sage-support] Re: Error with digraph plot and view

2023-06-03 Thread Matthias Koeppe
Try "make -j list-broken-packages", which may give instructions how to fix 
this

On Saturday, June 3, 2023 at 7:40:58 PM UTC-7 Jianping Pan wrote:

> Hi all,
>
> I'm using *SageMath version 10.1.beta1*, and I have dot2tex and graphviz 
> installed. I checked that following line produces a nice PDF of the tableau.
>
> sage: T = Tableau([[1,2,2], [2,3]]); view(T)
>
> However, I found that I can not plot or view any digraphs. Thanks!
>
> sage: G = graphs.PetersenGraph().to_directed()
> sage: G.plot()
> /Users/jianpingpan/sage/src/sage/repl/rich_output/display_manager.py:610: 
> RichReprWarning: Exception in _rich_repr_ while displaying object: 
> dlopen(/Users/jianpingpan/sage/local/lib/python3.8/site-packages/PIL/_
> imaging.cpython-38-darwin.so, 0x0002): Library not loaded: 
> '/usr/local/opt/libtiff/lib/libtiff.5.dylib'
>   Referenced from: 
> '/Users/jianpingpan/sage/local/lib/python3.8/site-packages/PIL/_
> imaging.cpython-38-darwin.so'
>   Reason: tried: '/usr/local/opt/libtiff/lib/libtiff.5.dylib' (no such 
> file), '/usr/lib/libtiff.5.dylib' (no such file), 
> '/usr/local/Cellar/libtiff/4.5.0/lib/libtiff.5.dylib' (no such file), 
> '/usr/lib/libtiff.5.dylib' (no such file)
>   warnings.warn(
>
> sage: latex(G)
> ImportError
>
> Specifically for the ImportError, it looks like the following PIL import 
> is broken
>
> sage: from PIL import Image
> ---
> ImportError  Traceback (most recent call last)
> Cell In [6], line 1
> > 1 from PIL import Image
>
> File ~/sage/local/lib/python3.8/site-packages/PIL/Image.py:89
>  80 MAX_IMAGE_PIXELS = int(1024 * 1024 * 1024 // 4 // 3)
>  83 try:
>  84 # If the _imaging C module is not present, Pillow will not 
> load.
>  85 # Note that other modules should not refer to _imaging 
> directly;
>  86 # import Image and use the Image.core variable instead.
>  87 # Also note that Image.core is not a publicly documented 
> interface,
>  88 # and should be considered private and subject to change.
> ---> 89 from . import _imaging as core
>  91 if __version__ != getattr(core, "PILLOW_VERSION", None):
>  92 raise ImportError(
>  93 "The _imaging extension was built for another version 
> of Pillow or PIL:\n"
>  94 f"Core version: {getattr(core, 'PILLOW_VERSION', 
> None)}\n"
>  95 f"Pillow version: {__version__}"
>  96 )
>
> ImportError: 
> dlopen(/Users/jianpingpan/sage/local/lib/python3.8/site-packages/PIL/_
> imaging.cpython-38-darwin.so, 0x0002): Library not loaded: 
> '/usr/local/opt/libtiff/lib/libtiff.5.dylib'
>   Referenced from: 
> '/Users/jianpingpan/sage/local/lib/python3.8/site-packages/PIL/_
> imaging.cpython-38-darwin.so'
>   Reason: tried: '/usr/local/opt/libtiff/lib/libtiff.5.dylib' (no such 
> file), '/usr/lib/libtiff.5.dylib' (no such file), 
> '/usr/local/Cellar/libtiff/4.5.0/lib/libtiff.5.dylib' (no such file), 
> '/usr/lib/libtiff.5.dylib' (no such file)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/71516cd7-558a-4cb8-8024-7963d7f225d8n%40googlegroups.com.


[sage-support] Re: Sage Crash Report

2023-05-26 Thread Matthias Koeppe
config.log please

On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote:

> Hi!
>
> I can't get sage to work when installing it with conda on a new MacBook 
> Pro with M2 chip and Ventura 13.3.
>
> I tried
> conda -n sage create sage=9.X python=3.Y
> for (X,Y) = (5,10), (8,10), (8,11).
> With Sage 9.5, I get the attached crash report.
> With Sage 9.8, I get the following linking error below.
>
> Cheers,
> Matthias
>
> (sage-py310) matthias@matthiass-air-2 ~ % sage
> ┌┐
> │ SageMath version 9.8, Release Date: 2023-02-11 │
> │ Using Python 3.10.11. Type "help()" for help.  │
> └┘
> ┏┓
> ┃ Warning: sage.all is not available; this is a limited REPL.┃
> ┗┛
> sage: import sage.all
> ---
> ImportError   Traceback (most recent call last)
> Cell In[1], line 1
> > 1 import sage.all
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/all.py:168
> 166 from sage.modules.allimport *
> 167 from sage.monoids.allimport *
> --> 168 from sage.algebras.all   import *
> 169 from sage.modular.allimport *
> 170 from sage.sat.allimport *
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/all.py:21
>   5 
> #*
>   6 #   Copyright (C) 2005 William Stein 
>   7 #
>(...)
>  17 #  http://www.gnu.org/licenses/
>  18 
> #*
>  19 from sage.misc.lazy_import import lazy_import
> ---> 21 import sage.algebras.catalog as algebras
>  23 from .quatalg.all import *
>  24 from .steenrod.all import *
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/catalog.py:84
>   1 r"""
>   2 Catalog of Algebras
>   3
>(...)
>  80   `
>  81 """
>  83 from sage.algebras.free_algebra import FreeAlgebra as Free
> ---> 84 from sage.algebras.quatalg.quaternion_algebra import 
> QuaternionAlgebra as Quaternion
>  85 from sage.algebras.steenrod.steenrod_algebra import 
> SteenrodAlgebra as Steenrod
>  86 from 
> sage.algebras.finite_dimensional_algebras.finite_dimensional_algebra import 
> FiniteDimensionalAlgebra as FiniteDimensional
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra.py:68
>  61 from operator import itemgetter
>  63 from .quaternion_algebra_element import (
>  64 QuaternionAlgebraElement_abstract,
>  65 QuaternionAlgebraElement_generic,
>  66 QuaternionAlgebraElement_rational_field,
>  67 QuaternionAlgebraElement_number_field)
> ---> 68 from . import quaternion_algebra_cython
>  70 from sage.modular.modsym.p1list import P1List
>  72 from sage.misc.cachefunc import cached_method
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/algebras/quatalg/quaternion_algebra_cython.pyx:1,
>  
> in init sage.algebras.quatalg.quaternion_algebra_cython 
> (build/cythonized/sage/algebras/quatalg/quaternion_algebra_cython.cpp:6484)()
> > 1 # distutils: language = c++
>   2 # distutils: libraries = gmp m NTL_LIBRARIES
>   3 # distutils: extra_compile_args = NTL_CFLAGS
>
> File 
> ~/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/matrix/matrix_integer_dense.pyx:1,
>  
> in init sage.matrix.matrix_integer_dense 
> (build/cythonized/sage/matrix/matrix_integer_dense.cpp:59322)()
> > 1 # -*- coding: utf-8 -*-
>   2 # distutils: extra_compile_args = NTL_CFLAGS M4RI_CFLAGS
>   3 # distutils: libraries = iml NTL_LIBRARIES gmp m CBLAS_LIBRARIES
>
> ImportError: 
> dlopen(/Users/matthias/anaconda3/envs/sage-py310/lib/python3.10/site-packages/sage/libs/linbox/
> linbox_flint_interface.cpython-310-darwin.so, 0x0002): symbol not found 
> in flat namespace 
> '__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm'
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/8654bcee-0e10-49f5-842e-42b49cacde0bn%40googlegroups.com.


[sage-support] Re: Error building 9.8 on Ubuntu 23.04

2023-04-09 Thread Matthias Koeppe
Try if "make sage_conf" fixes this problem.
If this persists, please post the file "config.log".

On Saturday, April 8, 2023 at 3:19:13 PM UTC-7 Eric Majzoub wrote:

> Thank you, this allows sage to complete the build. However, now I have 
> another problem. When I run sage from its install directory it gives the 
> error:
>
> AttributeError: module 'sage_conf' has no attribute '_main'
>
> And then strangely, it starts Sage 9.5, the version installed on my system 
> through apt. I didn't want to remove this version using apt because I 
> thought it would remove a lot of packages that I need for other programs. 
> Here is the full output.
>
> ./sage 
> Traceback (most recent call last): 
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 33, in <
> module> 
>sys.exit(load_entry_point('sage-conf', 'console_scripts', 
> 'sage-config')()) 
> ^^^ 
>
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 25, in i
> mportlib_load_entry_point 
>return next(matches).load() 
>    
>  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 204, in 
> load 
>return functools.reduce(getattr, attrs, module) 
>    
> AttributeError: module 'sage_conf' has no attribute '_main' 
> Traceback (most recent call last): 
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 33, in <
> module> 
>sys.exit(load_entry_point('sage-conf', 'console_scripts', 
> 'sage-config')()) 
> ^^^ 
>
>  File "/home/packages/SOURCE/sage/ehm_install/bin/././sage-config", line 
> 25, in i
> mportlib_load_entry_point 
>return next(matches).load() 
>    
>  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 204, in 
> load 
>return functools.reduce(getattr, attrs, module) 
>    
> AttributeError: module 'sage_conf' has no attribute '_main' 
> ┌┐ 
> │ SageMath version 9.5, Release Date: 2022-01-30 │ 
> │ Using Python 3.11.2. Type "help()" for help.   │ 
> └┘
>
>
>
> On Friday, April 7, 2023 at 4:53:15 PM UTC-5 John H Palmieri wrote:
>
>> Some recent versions of Singular don't seem to work with Sage. You could 
>> try "make distclean" (to start over) and "./configure 
>> --with-system-singular=no" to force Sage to build its own Singular. Then 
>> "make".
>>
>> On Friday, April 7, 2023 at 2:22:20 PM UTC-7 Eric Majzoub wrote:
>>
>>> Following the procedure outlined on the Sage install page for Ubuntu.
>>>
>>> make fails showing:
>>> Error building Sage. 
>>>
>>> The following package(s) may have failed to build (not necessarily 
>>> during this run of 'make all-start'): 
>>>
>>> * package: sagelib-9.8 
>>>  last build time: Apr 7 15:48 
>>>  log file:/home/packages/SOURCE/sage/logs/pkgs/sagelib-9.8.log
>>>
>>> The log file is attached. It shows that gcc exits with status 1, but 
>>> doesn't give any specific error output from gcc itself. It fails on 
>>> building multi_polynomial_libsingular.
>>>
>>> Any help is appreciated.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/d0d508eb-6bbd-4928-8c0f-f00c760976f8n%40googlegroups.com.


Re: [sage-support] Current advice for generic SageMath install advice

2023-03-29 Thread Matthias Koeppe


On Wednesday, March 29, 2023 at 1:33:07 PM UTC-7 Nils Bruin wrote:

On Wednesday, 29 March 2023 at 13:06:25 UTC-7 Matthias Koeppe wrote:

On Tuesday, March 28, 2023 at 10:18:23 PM UTC-7 Nils Bruin wrote:


[...] leads me to believe that it's probably nor possible to install 
pynormaliz via "make" in a binary distribution.


If you install Sage from a binary distribution, then there is no relation 
whatsoever to a source tree of Sage.

right ... with "make" it's indeed pretty clear that it's hard to find the 
place where you could even run this. With "sage -i" some idle hope was 
raised that that would still work in a binary distribution. If it doesn't 
(and/or if it never did) then that would be an extra reason to deprecate 
it. It is currently still provided:

$ sage --help
...
Sage-the-distribution options:
  --optional  -- list all optional packages that can be installed
  --experimental  -- list all experimental packages that can be 
installed
  --info [packages]   -- print the SPKG.txt or SPKG.rst of the given 
packages,
 and some additional information.
  -i [packages]   -- install the given Sage packages


This part of the help comes from build/bin/sage-site. Usually in binary 
distributions, this is not present.
On which distribution do you see this?

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/d36e0b58-7670-4582-b7b6-52056ad2a92an%40googlegroups.com.


Re: [sage-support] Current advice for generic SageMath install advice

2023-03-29 Thread Matthias Koeppe
On Tuesday, March 28, 2023 at 10:18:23 PM UTC-7 Nils Bruin wrote:


[...] leads me to believe that it's probably nor possible to install 
pynormaliz via "make" in a binary distribution.


If you install Sage from a binary distribution, then there is no relation 
whatsoever to a source tree of Sage.

[...] So "spkg" is only for source-based installs.


That's right.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c81b73af-1599-44fd-aa1c-d558d525a151n%40googlegroups.com.


Re: [sage-support] Current advice for generic SageMath install advice

2023-03-28 Thread Matthias Koeppe
On Monday, March 27, 2023 at 6:34:50 PM UTC-7 Nils Bruin wrote:

In my experience, sagelib needs rebuilding to interface with normaliz (I 
think it's "make normaliz pynormaliz" nowadays, or perhaps one needs a pip 
install).


No, there is no such build-time dependency. And "make pynormaliz" suffices; 
it builds normaliz and its dependencies.
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/16d7638d-7403-4467-a626-4e1b1515707en%40googlegroups.com.


[sage-support] Re: Equivalent System Packages command for homebrew?

2023-03-16 Thread Matthias Koeppe
This screenshot is from the "_prereq" spkg, which records the minimal 
packages for a from-source build of Sage.
Sage can be built using just the Xcode command-line tools, which is why 
nothing is displayed there.

On Tuesday, March 14, 2023 at 3:38:12 AM UTC-7 Rishitha Madhavaram wrote:

> [image: Screenshot 2023-03-07 at 5.13.17 AM.png]
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/0b26309a-7944-4f7e-8fed-75fd58c66a02n%40googlegroups.com.


[sage-support] Re: Backends for SemidefiniteProgram()

2023-02-19 Thread Matthias Koeppe
The way forward is via CVXpy. 
See https://github.com/sagemath/sage/pull/35120 (needs review); next 
step: https://github.com/sagemath/sage/issues/31962

On Friday, February 17, 2023 at 2:15:00 AM UTC-8 Peter Mueller wrote:

> Even though I installed the optional packages csdp and dsdp in Sage 9.8, 
> they do not seem to be available as backends for `SemidefiniteProgram()`. 
> At any rate, calling it with `solver='csdp'` or `solver='dsdp'` results in 
> the error message *ValueError: 'solver' should be set to 'CVXOPT', 
> 'Matrix', a class, or None (in which case the default one is used* which 
> does not help me further.
>
> By the way, I would consider it useful if an instance of 
> SemidefiniteProgram could export the program to some usable file, e.g. in 
> SDPA sparse format. (In analogy to the` write_mps()`  method for linear 
> programs.)
>
> -- Peter Mueller
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/692a54d1-0497-4ad4-8f8a-ca1706ab1ee3n%40googlegroups.com.


[sage-support] Re: Cannot build Sage 9.8 on Ubuntu 22.04.1 LTS

2023-01-30 Thread Matthias Koeppe
Disable Anaconda and read what "./configure" says at the end (these 
messages are for you)

On Sunday, January 29, 2023 at 2:07:52 PM UTC-8 hyunjo...@gmail.com wrote:

> Hello,
>
> I've been trying to build Sage 9.8 from source for development; I had 
> previously done so months ago, but I had not been able to do rebuild Sage 
> since pulling from the GitHub repository around late December/early 
> January. I've deleted the previous source/build directory that I had to try 
> building from source all over again to no avail.
>
> Attached is a copy of the logs subdirectory.
>
> Thank you for your help,
> Hyun Jong
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/16862f30-9744-4d43-a330-48b60cfbf4f3n%40googlegroups.com.


Re: [sage-support] Re: Sage 9.8 build error

2023-01-05 Thread Matthias Koeppe
I see the following error in sagelib-*.log:


#define LOCAL_HIREMAINDER register ulong hiremainder
  ^
sage/rings/polynomial/multi_polynomial_libsingular.cpp:35068:120: 
error: use of undeclared identifier 'pTakeOutComp1'; did you mean 
'pTakeOutComp'?
  __pyx_t_1 = ((PyObject 
*)__pyx_f_4sage_5rings_10polynomial_28multi_polynomial_libsingular_new_MP(__pyx_v_parent,
 
pTakeOutComp1((&(__pyx_v_res->m[__pyx_v_i])), __pyx_v_j))); if (


This is caused by a too new version of Singular installed in the system.

We have a fix (and upgrade of Singular) in 
https://trac.sagemath.org/ticket/34851; you can fetch and merge the branch 
of that ticket.

Alternatively, as a workaround, you can pass "--without-system-singular" as 
an option to "./configure"




On Wednesday, January 4, 2023 at 11:23:09 PM UTC-8 alexcha...@gmail.com 
wrote:

> I tried running 'make' again but am getting stuck at the same spot.
>
> I did not pass any arguments to configure. I don't have a good idea of how 
> this process works so i did not deviate from the instructions in README.md 
> (as far as I know). 
>
> I did indeed run source .homebrew-build-env before configure and make. 
>
> On Wed, Jan 4, 2023, 10:27 PM John H Palmieri  wrote:
>
>> Some observations:
>>
>> - It's showing a different error now.
>> - I find it unusual that more packages haven't been built before it tries 
>> to build sagelib. You could try "make" again and see how far it gets.
>> - config.log says 
>>
>> Invocation command line was
>>
>>   $ ./configure 
>> PKG_CONFIG_PATH=/opt/homebrew/opt/sqlite/lib/pkgconfig:/opt/homebrew/opt/readline/lib/pkgconfig:/opt/homebrew/opt/openblas/lib/pkgconfig:/opt/homebrew/lib/pkgconfig:
>>  
>> --no-create --no-recursion
>>
>> Did you pass these arguments to ./configure?
>>
>> - Did you "source .homebrew-build-env" before running "./configure" and 
>> "make"?
>>
>>
>> On Wednesday, January 4, 2023 at 2:59:01 PM UTC-8 alexcha...@gmail.com 
>> wrote:
>>
>>> After following all of the suggestions, I am still getting the error
>>>
>>> """
>>> Error building Sage.
>>>
>>> The following package(s) may have failed to build (not necessarily
>>> during this run of 'make all-start'):
>>>
>>> * package: sagelib-9.8.beta6
>>>   last build time: Jan 4 14:45
>>>   log file:   
>>>  /Users/alexchandler/Documents/GitHub/sage/logs/pkgs/sagelib-9.8.beta6.log
>>>
>>> It is safe to delete any log files and build directories, but they
>>> contain information that is helpful for debugging build problems.
>>> WARNING: If you now run 'make' again, the build directory of the
>>> same version of the package will, by default, be deleted. Set the
>>> environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
>>>
>>> make[1]: *** [all-start] Error 1
>>> make: *** [all] Error 2
>>> """
>>>
>>> This time there are only four packages with errors pointed out when I run
>>>
>>> grep -li "^Error" logs/pkgs/*
>>>
>>> so this is an improvement, but I am still unable to proceed. Any idea 
>>> how to fix the issue? I have attached logs, config.log, and a text file 
>>> with the 4 packages with errors.
>>>
>>> Thank you!
>>> Alex
>>>
>>> On Wednesday, January 4, 2023 at 11:35:39 AM UTC-8 John H Palmieri wrote:
>>>
 Many of the errors are discussed at 
 https://trac.sagemath.org/ticket/34838. You can probably avoid those 
 by running "make typing_extensions" before running "make".

 The most recent error seems to be for sagelib:

 ld: library not found for -lopenblas

 I assume that you followed the directions at the end of ./configure? It 
 is possible that some homebrew package got updated after running 
 ./configure, and now Sage is looking for the old one and can't find it. 
 Maybe you need to start over by running "make distclean"? Re-run 
 "./configure", then "make typing_extension", then "make".


 On Tuesday, January 3, 2023 at 10:56:01 PM UTC-8 alexcha...@gmail.com 
 wrote:

> Hello,
>
> I am trying to build Sage 9.8 from source on a 2021 Apple M1 laptop. I 
> have attached the logs for each attempt and also the packages with errors 
> as indicated by running 
>
> grep -li "^Error" logs/pkgs/*
>
> Thank you,
> Alex
>
>
> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-support...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/be9c7509-cba6-4fa2-9619-173161896767n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe 

Re: [sage-support] Re: WSL2 installation sage-ipython can't find packages

2022-10-17 Thread Matthias Koeppe
Details please - what is broken

On Saturday, October 15, 2022 at 9:13:06 PM UTC-7 florian...@gmail.com 
wrote:

> This pertains to installation of sage-9.7.tar.gz under WSL2. I've found it 
> necessary to run
>
> cp -r $HOME/sage/sage-9.7/src/sage/ext_data/
> $HOME/sage/local/lib/sage
>
> in order for various packages to pick up code in ext_data. I'm compiling 
> from source. I prefer
> to configure sage to compile as much as possible and to rely on 
> ubuntu/debian packages
> as little as possible.
>
> On Friday, October 14, 2022 at 1:56:05 PM UTC-4 dim...@gmail.com wrote:
>
>> I frankly don't understand Debian/Ubuntu packaging of SageMath. E.g. Sage 
>> 9.0 was never tested with Python 3.9, and their current version of 
>> cysignals. 
>>
>> Surely they are trying to backport our changes, but this is quite 
>> error-prone.
>>
>> Please use conda, or build from source, or use  Linux distro with much 
>> more up to date Sage, e.g.
>> archlinux or Gentoo.
>>
>>
>> HTH
>> Dima
>>
>>
>>
>>
>> On Fri, 14 Oct 2022, 18:25 Matthias Koeppe,  wrote:
>>
>>> Report Ubuntu packaging bugs to Ubuntu
>>
>>
>>>
>>> On Wednesday, October 12, 2022 at 10:17:31 PM UTC-7 kun.j...@gmail.com 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'm trying to run sage on WSL2 (Ubuntu focal 20.04.5 LTS), and after a 
>>>> fresh install (sadly only version 9.0), running `sage` gives the following 
>>>> error.
>>>>
>>>> ModuleNotFoundError: No module named 'sage.cpython.string'
>>>>
>>>> I happen to know that the packages are installed 
>>>> in /usr/lib/python3/dist-packages/, and sage/cpython/string.pyx is in 
>>>> there.
>>>>
>>>> What's particularly strange to me is that sage *can* find 
>>>> `sage.misc.banner` (which is in the same dist-packages location). 
>>>> Meanwhile, I can run `sage -python` and inspect `sys.path` manually (it 
>>>> has 
>>>> the right dist-packages path in it), but importing sage.all in that 
>>>> context 
>>>> fails with "ModuleNotFoundError: No module named 'cysignals.signals'" and 
>>>> similar with other imports.
>>>>
>>>> ➜  ~ ls -l */usr/lib/python3/dist-packages/sage*
>>>> .rw-r--r-- 2.3k root  1 Jan  2020 __init__.py
>>>> drwxr-xr-x- root 12 Oct 20:34 __pycache__
>>>> drwxr-xr-x- root 12 Oct 20:34 algebras
>>>> .rw-r--r--  12k root  8 Feb  2020 all.py
>>>> <...snipped...>
>>>> ➜  ~ sage -python
>>>> Python 3.9.14 (main, Sep  7 2022, 23:43:29)
>>>> [GCC 9.4.0] on linux
>>>> >>> import sys
>>>> >>> print(sys.path)
>>>> ['', '/usr/lib/python39.zip', '/usr/lib/python3.9', 
>>>> '/usr/lib/python3.9/lib-dynload', 
>>>> '/home/j2kun/.local/lib/python3.9/site-packages', 
>>>> '/usr/local/lib/python3.9/dist-packages', 
>>>> *'/usr/lib/python3/dist-packages'*]
>>>> >>> import sage.all
>>>> Traceback (most recent call last):
>>>>   File "", line 1, in 
>>>>   File "/usr/lib/python3/dist-packages/sage/all.py", line 77, in 
>>>> 
>>>> from cysignals.signals import (AlarmInterrupt, SignalError,
>>>>   File "/usr/lib/python3/dist-packages/cysignals/__init__.py", line 1, 
>>>> in 
>>>> from .signals import AlarmInterrupt, SignalError, init_cysignals  # 
>>>> noqa
>>>> ModuleNotFoundError: No module named 'cysignals.signals'* (jkun's 
>>>> note: it's there in** /usr/lib/python3/dist-packages/cysignals/)*
>>>>
>>>> I understand the recommendation is to use conda or build from source to 
>>>> get a version > 9.2, but is there a quick fix I can do to link the 
>>>> sage-python to these libraries? Maybe an existing trac issue I can read 
>>>> through workarounds? The reason I ask is because I'm working on a library 
>>>> that uses sage and it's a bit of a pain to fire up docker (and worse, the 
>>>> sagemath docker image had known issues (only just now seeing 
>>>> <https://trac.sagemath.org/ticket/34242#comment:21> that a new docker 
>>>> image got pushed; still, working in docker is a bit inconvenient))
>>>>
>>>> Any ideas? Further steps for investigation?
>>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-support...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-support/1545b076-f5f7-4a54-9959-1940e53e4b8dn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/sage-support/1545b076-f5f7-4a54-9959-1940e53e4b8dn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/eec7fd9d-25f5-4440-860f-58b1c7867149n%40googlegroups.com.


[sage-support] Re: WSL2 installation sage-ipython can't find packages

2022-10-14 Thread Matthias Koeppe
Report Ubuntu packaging bugs to Ubuntu

On Wednesday, October 12, 2022 at 10:17:31 PM UTC-7 kun.j...@gmail.com 
wrote:

> Hi all,
>
> I'm trying to run sage on WSL2 (Ubuntu focal 20.04.5 LTS), and after a 
> fresh install (sadly only version 9.0), running `sage` gives the following 
> error.
>
> ModuleNotFoundError: No module named 'sage.cpython.string'
>
> I happen to know that the packages are installed 
> in /usr/lib/python3/dist-packages/, and sage/cpython/string.pyx is in there.
>
> What's particularly strange to me is that sage *can* find 
> `sage.misc.banner` (which is in the same dist-packages location). 
> Meanwhile, I can run `sage -python` and inspect `sys.path` manually (it has 
> the right dist-packages path in it), but importing sage.all in that context 
> fails with "ModuleNotFoundError: No module named 'cysignals.signals'" and 
> similar with other imports.
>
> ➜  ~ ls -l */usr/lib/python3/dist-packages/sage*
> .rw-r--r-- 2.3k root  1 Jan  2020 __init__.py
> drwxr-xr-x- root 12 Oct 20:34 __pycache__
> drwxr-xr-x- root 12 Oct 20:34 algebras
> .rw-r--r--  12k root  8 Feb  2020 all.py
> <...snipped...>
> ➜  ~ sage -python
> Python 3.9.14 (main, Sep  7 2022, 23:43:29)
> [GCC 9.4.0] on linux
> >>> import sys
> >>> print(sys.path)
> ['', '/usr/lib/python39.zip', '/usr/lib/python3.9', 
> '/usr/lib/python3.9/lib-dynload', 
> '/home/j2kun/.local/lib/python3.9/site-packages', 
> '/usr/local/lib/python3.9/dist-packages', 
> *'/usr/lib/python3/dist-packages'*]
> >>> import sage.all
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python3/dist-packages/sage/all.py", line 77, in 
> from cysignals.signals import (AlarmInterrupt, SignalError,
>   File "/usr/lib/python3/dist-packages/cysignals/__init__.py", line 1, in 
> 
> from .signals import AlarmInterrupt, SignalError, init_cysignals  # 
> noqa
> ModuleNotFoundError: No module named 'cysignals.signals'* (jkun's note: 
> it's there in** /usr/lib/python3/dist-packages/cysignals/)*
>
> I understand the recommendation is to use conda or build from source to 
> get a version > 9.2, but is there a quick fix I can do to link the 
> sage-python to these libraries? Maybe an existing trac issue I can read 
> through workarounds? The reason I ask is because I'm working on a library 
> that uses sage and it's a bit of a pain to fire up docker (and worse, the 
> sagemath docker image had known issues (only just now seeing 
>  that a new docker 
> image got pushed; still, working in docker is a bit inconvenient))
>
> Any ideas? Further steps for investigation?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/1545b076-f5f7-4a54-9959-1940e53e4b8dn%40googlegroups.com.


Re: [sage-support] Re: Citing Sage properly in a paper

2022-09-05 Thread Matthias Koeppe


On Monday, September 5, 2022 at 1:09:59 AM UTC-7 Dima Pasechnik wrote:

> On Mon, Sep 5, 2022 at 4:06 AM Nils Bruin  wrote: 
> > On Sunday, 4 September 2022 at 10:31:42 UTC-7 george...@gmail.com 
> wrote: 
> >> I am about to submit a math paper to a journal. I would like to include 
> a proper citation for Sage. The Sage web page says: 
> >> 
> >> "Also, be sure to find out which components of SageMath, e.g. NumPy, 
> PARI, GAP, Sage-Combinat, that your calculation uses and properly attribute 
> those systems." 
> >> 
> >> My question is: which component am I using? 
> >> 
> >> I am doing the following: 
> >> 
> >> x, y, z = var('x, y, z') 
> >> factor(x^6+y^6) 
> >> factor(x^6-y^6) 
> >> expand((3*x^2+y^2)*(x^2+3*y^2)) 
>
> > 
> > That kind of use generally attracts a "using a computational algebra 
> system" since it's such a routine operation. In fact, people wouldn't blink 
> at no explanation at all or a comment about "manual computation". 
>
> But that's bad practice, detrimental in particular to CASs which don't 
> enjoy much funding, in general.


> Every time a grant application to support such a CAS is made, it's a 
> struggle to justify it, not the least due to lack of citations.


+1
 

>
> In this case (symbolics computations like this), it's 'ginac' alone, I 
> believe. 
>

When using factor, ginac/pynac may call out to Singular, 
see https://trac.sagemath.org/ticket/32613
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/87554a6c-77c6-4102-b6db-27d2431d5d3dn%40googlegroups.com.


[sage-support] Re: Sage 9.6 crash

2022-07-25 Thread Matthias Koeppe
>From the crash report:
ImportError: libflint-2.8.5.so: cannot open shared object file: No such 
file or directory 

Likely, a system update (apt-get upgrade) removed this version of the 
shared library.
Rebuild Sage from scratch.
See also https://trac.sagemath.org/ticket/34203


On Monday, July 25, 2022 at 7:28:50 AM UTC-7 Luis Finotti wrote:

> I've recently started having Sage (up to date) crash.
>
> The log is here: 
> https://web.math.utk.edu/~finotti/tmp/Sage_crash_report.txt
>
> The system is running Linux Debian Sid (up to date).  (I can provide more 
> details if necessary.)
>
> My guess is that it might be because I've installed/updated some packages 
> with pip.  Like jupyterlab, black, pandas, jupyterlab_code_formatter.  I 
> also updated pip.
>
> Here is the result of pip list from a Sage shell: 
> https://web.math.utk.edu/~finotti/tmp/sage_pip.txt
>
> This has also happened in a different system.  I could reinstall from 
> scratch.  On a third system, in which I am pretty sure I also 
> installed/updated the packages with pip (also running Debian Sid), I did 
> not have this problem.
>
> Any suggestions?  Is installing packages with pip a bad idea?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/0142d88e-ab66-4ef8-862c-b8030373f83en%40googlegroups.com.


[sage-support] Re: Latte-int: throw(NotGenericException) not allowed by ISO C++17 during build

2022-07-07 Thread Matthias Koeppe
That's https://trac.sagemath.org/ticket/33981

On Thursday, July 7, 2022 at 7:13:35 AM UTC-7 maksm...@gmail.com wrote:

> Hello, 
>
> I'm building latte-distro on ubuntu 22.04 (windows 10 dual boot, Ryzen 7 
> 5700h) for apt-installed sage 9.5 . ./configure executes properly but then 
> for make check the error is
>
> ExponentialSubst.h:67:3: error: ISO C++17 does not allow dynamic exception 
> specifications
>67 |   throw(NotGenericException);
>
> It appears to be a gcc version issue. Commenting out the offending lines 
> appears to bypass it but then sage cannot see the package.
>
> Also 
>
> sage -i  latte-int
>
> throws 
>
> No rule to make target 'all-toolchain'. Stop.
>
> Would appreciate any hints how to install the package
> Maks
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/97b04a57-6bb9-4d5a-9d16-0d9e6a85fdb7n%40googlegroups.com.


[sage-support] Re: Sage build form source giac giac-1.6.0.47p3 failed to build, help with external packages

2022-07-07 Thread Matthias Koeppe
This looks like https://trac.sagemath.org/ticket/31403

On Thursday, July 7, 2022 at 6:20:11 AM UTC-7 maksm...@gmail.com wrote:

> Hello, 
>
> I'm working on Ubuntu 22.04, dual booted to Windows 10 on separate 
> partition. The linux build is currently entirely fresh, after reinstalling, 
> there's only anaconda and sage deps installed. 
>
> I've succesfully installed sage from apt and conda (earlier also in WSL 
> and Windows on the other partition), but I could not install topcom and 
> latte_int external packages, either via sage -i (throws "no rule to make 
> target all-toolchain. Stop.") or via source builds either. 
>
> Instead I've tried to build sage itself fully from source code and after 
> 65m into "make" I got 
>
> [giac-1.6.0.47p3] /usr/bin/ld: icas.o: in function 
> `texmacs_graph_output(giac::gen const&, giac::gen&, 
> std::__cxx11::basic_string, 
> std::allocator >&, int, giac::context const*)':
> [giac-1.6.0.47p3] 
> /home/maksm/sage-9.5/local/var/tmp/sage/build/giac-1.6.0.47p3/src/src/icas.cc:263:
>  
> warning: the use of `tmpnam' is dangerous, better use `mkstemp'
> [giac-1.6.0.47p3] /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
> undefined reference to `clique_unweighted_find_single@CLIQUER_1'
> [giac-1.6.0.47p3] /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
> undefined reference to `graph_free@CLIQUER_1'
> [giac-1.6.0.47p3] /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: 
> undefined reference to `graph_new@CLIQUER_1'
> [giac-1.6.0.47p3] collect2: error: ld returned 1 exit status
> [giac-1.6.0.47p3] make[7]: *** [Makefile:775: icas] Error 1
> [giac-1.6.0.47p3] make[6]: *** [Makefile:505: all-recursive] Error 1
> [giac-1.6.0.47p3] make[5]: *** [Makefile:435: all] Error 2
> [giac-1.6.0.47p3] 
> 
> [giac-1.6.0.47p3] Error building giac-1.6.0.47p3
> [giac-1.6.0.47p3] 
> 
> [giac-1.6.0.47p3] 
> [giac-1.6.0.47p3] real7m44.336s
> [giac-1.6.0.47p3] user7m29.302s
> [giac-1.6.0.47p3] sys0m13.064s
> [giac-1.6.0.47p3] 
> 
> [giac-1.6.0.47p3] Error installing package giac-1.6.0.47p3
> [giac-1.6.0.47p3] 
> **
>
> see attached the relevant logs. I left it as it was (I'm not very 
> experienced with this kind of problems) and would really appreciate some 
> hints on both this build and external packages.
>
> Thank you in advance, 
> Maks
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/d324f28d-2681-4dc2-bd8b-bdae803e6517n%40googlegroups.com.


[sage-support] Re: building SageMath on macOS

2022-06-28 Thread Matthias Koeppe
I've opened https://trac.sagemath.org/ticket/34098 for this

On Tuesday, June 21, 2022 at 2:58:26 PM UTC-7 list...@gmail.com wrote:

>
> When building SageMath on macOS from source, I think it is important to 
> stress that
> $ source .homebrew-build-env
> must be done before
> $ ./configure
> (I have not found this in the instructions, and I have spent some time 
> trying to guess why ./configure did not find system packages from Homebrew).
>
> I could make a note myself, but I am not sure where and how.
>
> Guillermo
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/e1280c17-f584-432e-afe5-4ad4189cb054n%40googlegroups.com.


[sage-support] Re: Brial error

2022-06-27 Thread Matthias Koeppe
>From config.log:

configure:7443: checking for pkg-config 
configure:7466: found /mnt/c/Strawberry/perl/bin/pkg-config 
configure:7478: result: /mnt/c/Strawberry/perl/bin/pkg-config 

It's picking up pkg-config from your Windows install. Remote 
/mnt/c/Strawberry/perl/bin/ from your PATH, and/or install the packages 
that the Sage top-level configure script recommends to install.


On Wednesday, June 22, 2022 at 5:19:21 AM UTC-7 mishel@gmail.com wrote:

> configure: error: in 
> `/mnt/c/sage/local/var/tmp/sage/build/brial-1.2.8/src':
> [brial-1.2.8] configure: error: The pkg-config script could not be found 
> or is too old.  Make sure it
> [brial-1.2.8] is in your PATH or set the PKG_CONFIG environment variable 
> to the full
> [brial-1.2.8] path to pkg-config.
>
> Building sage from source code on Ubuntu 22.04 under wsl. 
>
> Can not fix this. Tried 
> sudo apt-get install libbrial-dev libbrial-groebner-dev
> sudo apt-get install python3-brial
>
> That did not help
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/f1c9c9c3-16f5-470c-8a8d-e023d0bb2ac1n%40googlegroups.com.


[sage-support] Global Virtual Sage Days 112.358, June 1-3 - Call for Participation

2022-05-16 Thread Matthias Koeppe
An online event on open-source mathematical software
with the SageMath user and developer community
https://wiki.sagemath.org/days112.358
50 hours around the world
Register today
It's free

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/6c5df215-c447-4d02-8473-229c72ca4bdfn%40googlegroups.com.


[sage-support] Re: Fedora 36 Update problem

2022-05-14 Thread Matthias Koeppe
Report Fedora packaging bugs to Fedora.

On Saturday, May 14, 2022 at 1:14:00 PM UTC-7 marks...@googlemail.com wrote:

> Hello all,
>
> I recently installed SageMath on my Fedora machine using dnf install 
> sagemath.
> The install went fine and I can use the sage interactive shell just fine. 
> Today I wanted to use a sage command from a Python script. Typing "from 
> sage.all import *" (or import sage.all) produced an error:
> ModuleNotFoundError: No module named 'memory_allocator'
>
> So I went looking in DNF.
>
> I was surprised to find all the errors listed below. Is this because I now 
> have Fedora 36 and the packages have not yet caught up? Is there anything I 
> can do?
>
> Thanks in advance for any help or suggestions...
>
> sudo dnf update
> Last metadata expiration check: 1:52:48 ago on Sat 14 May 2022 18:57:19 
> BST.
> Dependencies resolved.
>
>  Problem 1: package polymake-4.6-5.fc36.x86_64 requires 
> libpolys-4.2.0.so()(64bit), 
> but none of the providers can be installed
>   - cannot install both Singular-libpolys-4.2.1p3-1.fc36.x86_64 and 
> Singular-libpolys-4.2.0p3-3.fc36.x86_64
>   - cannot install the best update candidate for package 
> polymake-4.6-5.fc36.x86_64
>   - cannot install the best update candidate for package 
> Singular-libpolys-4.2.0p3-3.fc36.x86_64
>  Problem 2: problem with installed package polymake-4.6-5.fc36.x86_64
>   - package polymake-4.6-5.fc36.x86_64 requires 
> libSingular-4.2.0.so()(64bit), 
> but none of the providers can be installed
>   - cannot install both Singular-libs-4.2.1p3-1.fc36.x86_64 and 
> Singular-libs-4.2.0p3-3.fc36.x86_64
>   - cannot install the best update candidate for package 
> Singular-libs-4.2.0p3-3.fc36.x86_64
>  Problem 3: package gap-pkg-polymaking-0.8.6-3.fc36.noarch requires 
> polymake, but none of the providers can be installed
>   - polymake-4.6-5.fc36.i686 has inferior architecture
>   - polymake-4.6-4.fc36.i686 has inferior architecture
>   - package polymake-4.6-5.fc36.x86_64 requires 
> libsingular_resources-4.2.0.so()(64bit), but none of the providers can be 
> installed
>   - package polymake-4.6-4.fc36.x86_64 requires 
> libsingular_resources-4.2.0.so()(64bit), but none of the providers can be 
> installed
>   - cannot install both factory-4.2.1p3-1.fc36.x86_64 and 
> factory-4.2.0p3-3.fc36.x86_64
>   - cannot install the best update candidate for package 
> gap-pkg-polymaking-0.8.6-3.fc36.noarch
>   - cannot install the best update candidate for package 
> factory-4.2.0p3-3.fc36.x86_64
>  Problem 4: package sagemath-core-9.5-2.fc36.x86_64 requires 
> gap-pkg-polymaking, but none of the providers can be installed
>   - package gap-pkg-polymaking-0.8.6-3.fc36.noarch requires polymake, but 
> none of the providers can be installed
>   - package polymake-4.6-4.fc36.i686 requires 
> libsingular_resources-4.2.0.so, but none of the providers can be installed
>   - package polymake-4.6-5.fc36.i686 requires 
> libsingular_resources-4.2.0.so, but none of the providers can be installed
>   - package polymake-4.6-5.fc36.x86_64 requires libpolys-4.2.0.so()(64bit), 
> but none of the providers can be installed
>   - package polymake-4.6-4.fc36.x86_64 requires libpolys-4.2.0.so()(64bit), 
> but none of the providers can be installed
>   - package factory-4.2.0p3-3.fc36.i686 requires factory-gftables = 
> 4.2.0p3-3.fc36, but none of the providers can be installed
>   - cannot install both Singular-libpolys-4.2.1p3-1.fc36.x86_64 and 
> Singular-libpolys-4.2.0p3-3.fc36.x86_64
>   - cannot install both factory-gftables-4.2.1p3-1.fc36.noarch and 
> factory-gftables-4.2.0p3-3.fc36.noarch
>   - package Singular-4.2.1p3-1.fc36.x86_64 requires 
> libpolys-4.2.1.so()(64bit), 
> but none of the providers can be installed
>   - cannot install the best update candidate for package 
> pynac-0.7.29-2.fc36.x86_64
>   - cannot install the best update candidate for package 
> factory-gftables-4.2.0p3-3.fc36.noarch
>   - cannot install the best update candidate for package 
> Singular-4.2.0p3-3.fc36.x86_64
>  Problem 5: package sagemath-core-9.5-2.fc36.x86_64 requires 
> gap-pkg-polymaking, but none of the providers can be installed
>   - package gap-pkg-polymaking-0.8.6-3.fc36.noarch requires polymake, but 
> none of the providers can be installed
>   - package polymake-4.6-4.fc36.i686 requires libpolys-4.2.0.so, but none 
> of the providers can be installed
>   - package polymake-4.6-5.fc36.i686 requires libpolys-4.2.0.so, but none 
> of the providers can be installed
>   - Singular-libpolys-4.2.0p3-3.fc36.i686 has inferior architecture
>   - package polymake-4.6-5.fc36.x86_64 requires libpolys-4.2.0.so()(64bit), 
> but none of the providers can be installed
>   - package polymake-4.6-4.fc36.x86_64 requires libpolys-4.2.0.so()(64bit), 
> but none of the providers can be installed
>   - cannot install both Singular-libpolys-4.2.1p3-1.fc36.x86_64 and 
> Singular-libpolys-4.2.0p3-3.fc36.x86_64
>   - package sagemath-core-9.5-2.fc36.x86_64 requires 
> 

[sage-support] Re: Sage ImportError: canot load Singular library

2022-05-11 Thread Matthias Koeppe
Report Fedora packaging bugs to Fedora

On Wednesday, May 11, 2022 at 3:23:15 AM UTC-7 jacovant...@gmail.com wrote:

> I am running Fedora 36 (had the same issue in Fedora 35) on a Lenovo 
> IdeaPad. After installing sage using dnf I tried running it but it failed 
> due to: "ImportError: cannot load Singular library from libSingular.so 
> (b'libSingular.so: cannot open shared object file: No such file or 
> directory')". The full error report is:
>
> Error in sys.excepthook:
> Traceback (most recent call last):
>   File "/usr/lib64/python3.10/pathlib.py", line 1303, in is_dir
> return S_ISDIR(self.stat().st_mode)
> AttributeError: 'str' object has no attribute 'stat'
>
> Original exception was:
> Traceback (most recent call last):
>   File "/usr/lib64/sagemath/local/bin/sage-ipython", line 15, in 
> app.initialize()
>   File 
> "/home/jacovantonder/.local/lib/python3.10/site-packages/traitlets/config/application.py",
>  
> line 88, in inner
> return method(app, *args, **kwargs)
>   File "/usr/lib/python3.10/site-packages/IPython/terminal/ipapp.py", line 
> 276, in initialize
> self.init_shell()
>   File "/usr/lib64/python3.10/site-packages/sage/repl/interpreter.py", 
> line 789, in init_shell
> self.shell.extension_manager.load_extension(SAGE_EXTENSION)
>   File "/usr/lib/python3.10/site-packages/IPython/core/extensions.py", 
> line 76, in load_extension
> return self._load_extension(module_str)
>   File "/usr/lib/python3.10/site-packages/IPython/core/extensions.py", 
> line 99, in _load_extension
> if self._call_load_ipython_extension(mod):
>   File "/usr/lib/python3.10/site-packages/IPython/core/extensions.py", 
> line 151, in _call_load_ipython_extension
> mod.load_ipython_extension(self.shell)
>   File "/usr/lib64/python3.10/site-packages/sage/repl/__init__.py", line 
> 5, in load_ipython_extension
> sage.repl.ipython_extension.load_ipython_extension(*args)
>   File 
> "/usr/lib64/python3.10/site-packages/sage/repl/ipython_extension.py", line 
> 617, in wrapper
> result = func(*args, **kwargs)
>   File 
> "/usr/lib64/python3.10/site-packages/sage/repl/ipython_extension.py", line 
> 630, in load_ipython_extension
> SageCustomizations(shell=ip)
>   File 
> "/usr/lib64/python3.10/site-packages/sage/repl/ipython_extension.py", line 
> 434, in __init__
> import sage.all # until sage's import hell is fixed
>   File "/usr/lib64/python3.10/site-packages/sage/all.py", line 131, in 
> 
> from sage.rings.all  import *
>   File "/usr/lib64/python3.10/site-packages/sage/rings/all.py", line 87, 
> in 
> from .qqbar import (AlgebraicRealField, AA,
>   File "/usr/lib64/python3.10/site-packages/sage/rings/qqbar.py", line 
> 2810, in 
> QQxy = QQ['x', 'y']
>   File "sage/structure/parent.pyx", line 1276, in 
> sage.structure.parent.Parent.__getitem__
>   File "/usr/lib64/python3.10/site-packages/sage/categories/rings.py", 
> line 1177, in __getitem__
> return PolynomialRing(self, elts)
>   File 
> "/usr/lib64/python3.10/site-packages/sage/rings/polynomial/polynomial_ring_constructor.py",
>  
> line 647, in PolynomialRing
> return _multi_variate(base_ring, names, **kwds)
>   File 
> "/usr/lib64/python3.10/site-packages/sage/rings/polynomial/polynomial_ring_constructor.py",
>  
> line 775, in _multi_variate
> from sage.rings.polynomial.multi_polynomial_libsingular import 
> MPolynomialRing_libsingular
>   File "sage/rings/polynomial/multi_polynomial_libsingular.pyx", line 1, 
> in init sage.rings.polynomial.multi_polynomial_libsingular
>   File "sage/libs/singular/singular.pyx", line 1558, in init 
> sage.libs.singular.singular
>   File "sage/libs/singular/singular.pyx", line 1532, in 
> sage.libs.singular.singular.init_libsingular
> ImportError: cannot load Singular library from libSingular.so 
> (b'libSingular.so: cannot open shared object file: No such file or 
> directory')
>
> I've had issues with installing sage with conda as well. Not being able to 
> get the kernel to connect in Jupyter.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/a8ccee00-8e45-4392-99c3-4ecefee9541dn%40googlegroups.com.


Re: [sage-support] ./sage -br fails

2022-04-26 Thread Matthias Koeppe
I have a fix in  https://trac.sagemath.org/ticket/33587, please test

On Monday, April 25, 2022 at 2:49:04 AM UTC-7 list...@gmail.com wrote:

>
> Thanks Matthias.
>
> This is on the latest develop branch.
>
> I have added a comment to the ticket you mention.
>
> Guillermo
>
> On Mon, 25 Apr 2022 at 04:32, Matthias Koeppe  
> wrote:
>
>> Which version of Sage is this?
>> We fixed a bug like this recently that showed up when the environment 
>> variable MAKE was set in a particular way.
>> See also https://trac.sagemath.org/ticket/33587
>>
>> On Sunday, April 24, 2022 at 3:17:08 AM UTC-7 list...@gmail.com wrote:
>>
>>>
>>> Thanks, Maxime.
>>>
>>> Here is what I did.
>>> Starting from scratch, cloned develop branch, make, make pytest, make 
>>> ptestlong with no problems.
>>> New branch with a very minor modification in one file (typo in a doc 
>>> string).
>>> So I think this applies:
>>>
>>> *Rebuilding Sage*
>>> Once you have made any changes you of course want to build Sage and try 
>>> out your edits. As long as you only modified the Sage library (that is, 
>>> Python and Cython files under src/sage/...) you just have to run:
>>> ./sage -br
>>> to rebuild the Sage library and then start Sage. This should be quite 
>>> fast. If you made changes to third-party packages, then you have to run
>>> make build
>>> as if you were installing Sage from scratch.
>>>
>>>  Of course make build works, but my question is why ./sage -br fails 
>>> with
>>> /bin/sh: @cd: command not found
>>>
>>> Guillermo
>>>
>>> On Sun, 24 Apr 2022 at 11:30, Maxime Bombar  wrote:
>>>
>>>> On 4/24/22 00:37, G. M.-S. wrote:
>>>> >
>>>> > Following the advice in
>>>> >
>>>> > 
>>>> https://doc.sagemath.org/html/en/developer/walk_through.html#rebuilding-sage
>>>> >
>>>> > when trying
>>>> >
>>>> > ./sage -br
>>>> >
>>>> > I get
>>>> >
>>>> > [...]
>>>> > ***
>>>> > /bin/sh: @cd: command not found
>>>> > make: *** [sagelib-SAGE_VENV-no-deps] Error 127
>>>> >
>>>> > real 0m0.029s
>>>> > user 0m0.024s
>>>> > sys 0m0.003s
>>>> > ***
>>>> > Error building Sage.
>>>> >
>>>> > The following package(s) may have failed to build (not necessarily
>>>> > during this run of 'make sagelib-no-deps'):
>>>> >
>>>> > It is safe to delete any log files [...]
>>>> >
>>>> > What can I do?
>>>> >
>>>> > Guillermo
>>>> >
>>>> Hi Guillermo,
>>>>
>>>> if you have upgraded your system, especially python version, and/or 
>>>> other Sage dependencies, it might be necessary to rebuild sage from 
>>>> scratch, with a `make build`.
>>>>
>>>> -- 
>>>> Maxime
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-support...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/275b0149-3c16-4b83-a196-a8d0f1170ecen%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sage-support/275b0149-3c16-4b83-a196-a8d0f1170ecen%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/9e277765-884e-4490-84a2-9f3b82e1c3cbn%40googlegroups.com.


Re: [sage-support] ./sage -br fails

2022-04-24 Thread Matthias Koeppe
Which version of Sage is this?
We fixed a bug like this recently that showed up when the environment 
variable MAKE was set in a particular way.
See also https://trac.sagemath.org/ticket/33587

On Sunday, April 24, 2022 at 3:17:08 AM UTC-7 list...@gmail.com wrote:

>
> Thanks, Maxime.
>
> Here is what I did.
> Starting from scratch, cloned develop branch, make, make pytest, make 
> ptestlong with no problems.
> New branch with a very minor modification in one file (typo in a doc 
> string).
> So I think this applies:
>
> *Rebuilding Sage*
> Once you have made any changes you of course want to build Sage and try 
> out your edits. As long as you only modified the Sage library (that is, 
> Python and Cython files under src/sage/...) you just have to run:
> ./sage -br
> to rebuild the Sage library and then start Sage. This should be quite 
> fast. If you made changes to third-party packages, then you have to run
> make build
> as if you were installing Sage from scratch.
>
>  Of course make build works, but my question is why ./sage -br fails with
> /bin/sh: @cd: command not found
>
> Guillermo
>
> On Sun, 24 Apr 2022 at 11:30, Maxime Bombar  wrote:
>
>> On 4/24/22 00:37, G. M.-S. wrote:
>> >
>> > Following the advice in
>> >
>> > 
>> https://doc.sagemath.org/html/en/developer/walk_through.html#rebuilding-sage
>> >
>> > when trying
>> >
>> > ./sage -br
>> >
>> > I get
>> >
>> > [...]
>> > ***
>> > /bin/sh: @cd: command not found
>> > make: *** [sagelib-SAGE_VENV-no-deps] Error 127
>> >
>> > real 0m0.029s
>> > user 0m0.024s
>> > sys 0m0.003s
>> > ***
>> > Error building Sage.
>> >
>> > The following package(s) may have failed to build (not necessarily
>> > during this run of 'make sagelib-no-deps'):
>> >
>> > It is safe to delete any log files [...]
>> >
>> > What can I do?
>> >
>> > Guillermo
>> >
>> Hi Guillermo,
>>
>> if you have upgraded your system, especially python version, and/or 
>> other Sage dependencies, it might be necessary to rebuild sage from 
>> scratch, with a `make build`.
>>
>> -- 
>> Maxime
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/275b0149-3c16-4b83-a196-a8d0f1170ecen%40googlegroups.com.


[sage-support] Re: Removing packages and different versions of python

2022-04-15 Thread Matthias Koeppe
On Friday, April 15, 2022 at 12:39:23 AM UTC-7 Jean-Florent Raymond wrote:

> In order to test something I would like to remove from my sage install a 
> python package that I installed (and updated) some time ago. 
>
> First question: 
> How can I remove a package installed with "sage -i"? I found 
> instructions in the doc to install packages, but nothing to remove them. 
> Is "sage -i" the same as "sage -pip install" (and "pip install" in a 
> "sage -sh" session), so I can simply do "sage -pip uninstall"?


To uninstall a package SPKG, use either "make SPKG-clean" or "make 
SPKG-uninstall" - depending on the package source type (see 
https://doc.sagemath.org/html/en/developer/packaging.html#package-source-types).
 
(We are in the process of unifying this - 
https://trac.sagemath.org/ticket/29097)

When checking if there remain some files named after this package after 
> the "sage -pip uninstall" command, I can see that the package is still 
> installed in: 
>
> sage/local/lib/python3.7/site-packages/ 
> sage/local/lib/python3.9/site-packages/ 
>
> I guess because I installed it when the python version of my sage 
> install was 3.7 or 3.9 (currently it is 3.10.3).

I don't think there is a reason to keep this, hence my second question : 
> how to remove this given that I don't have python3.7 or python3.9 
> anymore in sage-sh ? Can I just rm everything in 
> sage/local/lib/python3.7 and sage/local/lib/python3.9?


Yes, you can safely "rm" it.
 

> Last question: what does "spkg" mean :) ?


I think it just means "Sage package".
 

> Is it just any package that 
> can be installed to use with Sage, some of which are standard python 
> (pip-installable) packages and some with different install scripts?
>

Yes.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/1ad41f4b-966d-4597-bb11-fd154ffc0723n%40googlegroups.com.


[sage-support] Re: OS X 12.3 intel: scipy fails to build

2022-03-17 Thread Matthias Koeppe
Thanks for testing! I have opened https://trac.sagemath.org/ticket/33522 
for the upgrade

On Thursday, March 17, 2022 at 3:00:24 PM UTC-7 John H Palmieri wrote:

> "./sage -pip install -U pythran" seems to have worked. I checked Sage's 
> pythran log and didn't see anything suspicious, for what that's worth.
>
> On Thursday, March 17, 2022 at 2:34:56 PM UTC-7 Matthias Koeppe wrote:
>
>> It would be worth checking whether "./sage -pip install -U pythran" or 
>> "./sage -pip install -U git+https://github.com/serge-sans-paille/pythran; 
>> fixes this issue
>>
>> On Thursday, March 17, 2022 at 2:01:49 PM UTC-7 John H Palmieri wrote:
>>
>>> Since upgrading to OS X 12.3 a few days ago, along with the 
>>> corresponding Xcode and command line tools, I have been unable to build 
>>> scipy. The end of the log file says
>>>
>>>   Building wheel for scipy (pyproject.toml): finished with status 'error'
>>>   ERROR: Failed building wheel for scipy
>>>
>>> A little before that:
>>>
>>>   
>>> /Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.6.beta5/local/var/lib/sage/venv-python3.10.2/lib/python3.10/site-packages/pythran/pythonic/types/str.hpp:417:12:
>>>  
>>> error: no matching constructor for initialization of 'typename 
>>> str::reverse_iterator' (aka 'reverse_iterator<(anonymous 
>>> namespace)::pythonic::types::string_iterator>')
>>>   return {data->rend()};
>>>  ^~
>>>
>>> Log files attached. I've tried this using all of my installed homebrew 
>>> packages and also using (as you can see in config.log) 
>>> "--with-system-python3=no", same result either way. Any suggestions?
>>>
>>> -- 
>>> John
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/67895c1c-732f-4849-9ed5-b01745c64286n%40googlegroups.com.


[sage-support] Re: OS X 12.3 intel: scipy fails to build

2022-03-17 Thread Matthias Koeppe
It would be worth checking whether "./sage -pip install -U pythran" or 
"./sage -pip install -U git+https://github.com/serge-sans-paille/pythran; 
fixes this issue

On Thursday, March 17, 2022 at 2:01:49 PM UTC-7 John H Palmieri wrote:

> Since upgrading to OS X 12.3 a few days ago, along with the corresponding 
> Xcode and command line tools, I have been unable to build scipy. The end of 
> the log file says
>
>   Building wheel for scipy (pyproject.toml): finished with status 'error'
>   ERROR: Failed building wheel for scipy
>
> A little before that:
>
>   
> /Users/palmieri/Desktop/Sage/sage_builds/TESTING/sage-9.6.beta5/local/var/lib/sage/venv-python3.10.2/lib/python3.10/site-packages/pythran/pythonic/types/str.hpp:417:12:
>  
> error: no matching constructor for initialization of 'typename 
> str::reverse_iterator' (aka 'reverse_iterator<(anonymous 
> namespace)::pythonic::types::string_iterator>')
>   return {data->rend()};
>  ^~
>
> Log files attached. I've tried this using all of my installed homebrew 
> packages and also using (as you can see in config.log) 
> "--with-system-python3=no", same result either way. Any suggestions?
>
> -- 
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/18152f28-e3fd-4cd0-8315-c834660f249fn%40googlegroups.com.


[sage-support] Re: How to create a new virtual environment based on an existing sage installation

2022-03-12 Thread Matthias Koeppe
https://trac.sagemath.org/ticket/33440 fixes the problem and is waiting for 
review.

On Tuesday, March 1, 2022 at 11:07:50 AM UTC-8 Matthias Koeppe wrote:

> The particular error that you are running into comes from Singular not 
> being in PATH.
>
> Use "sage -sh" to enter a shell in which SAGE_LOCAL/bin has been added to 
> PATH.
> Then you can activate the venv as you did before.
>
>
>
> On Tuesday, March 1, 2022 at 10:45:00 AM UTC-8 m.derick...@gmail.com 
> wrote:
>
>> Hi All,
>>
>> I am wondering what the best way is to create a new virtual environment 
>> where I can import stuff from an already existing sage installation:
>>
>> I tried the following using sage 9.5.beta9
>>
>> $ sage -python3 -m venv --system-site-packages venv
>> $ source venv/bin/activate
>> (venv) $ python3
>> Python 3.9.9 (main, Dec 25 2021, 18:25:51)
>> [GCC 9.3.0] on linux 
>> Type "help", "copyright", "credits" or "license" for more information. 
>> >>> from sage.all import * 
>> Traceback (most recent call last): 
>> File "", line 1, in  
>> File 
>> "/scratch/home/mderickx/sages/sage/local/var/lib/sage/venv-python3.9.9/lib/python3.9/site-packages/sage/all.py",
>>  
>> line 126, in  
>> from sage.rings.all import * 
>> File 
>> "/scratch/home/mderickx/sages/sage/local/var/lib/sage/venv-python3.9.9/lib/python3.9/site-packages/sage/rings/all.py",
>>  
>> line 87, in  
>> ...
>> ...
>> File "sage/rings/polynomial/multi_polynomial_libsingular.pyx", line 1, in 
>> init sage.rings.polynomial.multi_polynomial_libsingular 
>> (build/cythonized/sage/rings/polynomial/multi_polynomial_libsingular.cpp:50020)
>>  
>>
>> File "sage/libs/singular/singular.pyx", line 1558, in init 
>> sage.libs.singular.singular 
>> (build/cythonized/sage/libs/singular/singular.cpp:15747) 
>> File "sage/libs/singular/singular.pyx", line 1525, in 
>> sage.libs.singular.singular.init_libsingular 
>> (build/cythonized/sage/libs/singular/singular.cpp:12865) 
>> File 
>> "/scratch/home/mderickx/sages/sage/local/var/lib/sage/venv-python3.9.9/lib/python3.9/posixpath.py",
>>  
>> line 152, in dirname 
>> p = os.fspath(p) 
>> TypeError: expected str, bytes or os.PathLike object, not NoneType
>>
>> But as you can see this new venv is not created in such a way that sage 
>> the library is useable (probably because certain sage related environment 
>> variables are not set).
>>
>> So what is the best way to get around this?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/2b6fdb69-9fa4-4a48-bff4-f14f01a289ean%40googlegroups.com.


[sage-support] Re: How to create a new virtual environment based on an existing sage installation

2022-03-01 Thread Matthias Koeppe
The particular error that you are running into comes from Singular not 
being in PATH.

Use "sage -sh" to enter a shell in which SAGE_LOCAL/bin has been added to 
PATH.
Then you can activate the venv as you did before.



On Tuesday, March 1, 2022 at 10:45:00 AM UTC-8 m.derick...@gmail.com wrote:

> Hi All,
>
> I am wondering what the best way is to create a new virtual environment 
> where I can import stuff from an already existing sage installation:
>
> I tried the following using sage 9.5.beta9
>
> $ sage -python3 -m venv --system-site-packages venv
> $ source venv/bin/activate
> (venv) $ python3
> Python 3.9.9 (main, Dec 25 2021, 18:25:51)
> [GCC 9.3.0] on linux 
> Type "help", "copyright", "credits" or "license" for more information. 
> >>> from sage.all import * 
> Traceback (most recent call last): 
> File "", line 1, in  
> File 
> "/scratch/home/mderickx/sages/sage/local/var/lib/sage/venv-python3.9.9/lib/python3.9/site-packages/sage/all.py",
>  
> line 126, in  
> from sage.rings.all import * 
> File 
> "/scratch/home/mderickx/sages/sage/local/var/lib/sage/venv-python3.9.9/lib/python3.9/site-packages/sage/rings/all.py",
>  
> line 87, in  
> ...
> ...
> File "sage/rings/polynomial/multi_polynomial_libsingular.pyx", line 1, in 
> init sage.rings.polynomial.multi_polynomial_libsingular 
> (build/cythonized/sage/rings/polynomial/multi_polynomial_libsingular.cpp:50020)
>  
>
> File "sage/libs/singular/singular.pyx", line 1558, in init 
> sage.libs.singular.singular 
> (build/cythonized/sage/libs/singular/singular.cpp:15747) 
> File "sage/libs/singular/singular.pyx", line 1525, in 
> sage.libs.singular.singular.init_libsingular 
> (build/cythonized/sage/libs/singular/singular.cpp:12865) 
> File 
> "/scratch/home/mderickx/sages/sage/local/var/lib/sage/venv-python3.9.9/lib/python3.9/posixpath.py",
>  
> line 152, in dirname 
> p = os.fspath(p) 
> TypeError: expected str, bytes or os.PathLike object, not NoneType
>
> But as you can see this new venv is not created in such a way that sage 
> the library is useable (probably because certain sage related environment 
> variables are not set).
>
> So what is the best way to get around this?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/f3a37677-442c-4953-aa06-e2dda8118c4cn%40googlegroups.com.


Re: [sage-support] Re: Basic Stats deprecated?

2022-02-28 Thread Matthias Koeppe
The functionality has not been removed. We can do a slower deprecation 
here, i.e., not remove the module after a year, but perhaps after n years.

On Monday, February 28, 2022 at 3:26:08 PM UTC-8 John H Palmieri wrote:

> Should there be a small list of functions which we import automatically? 
> For example in sage.all we could do: "from numpy import mean, median". It 
> seems strange to not have a top-level "mean" or "median" function, given 
> all of the other esoteric top-level functions.
>
>
> On Friday, February 25, 2022 at 10:28:17 PM UTC-8 Matthias Koeppe wrote:
>
>> On Friday, February 25, 2022 at 8:32:39 PM UTC-8 wst...@gmail.com wrote:
>>
>>> Also, if you want to argue that users should explicitly import 
>>> everything...
>>
>>
>> No, that's not what I'm arguing. 
>>
>> The deprecation of the basic_stats module happened because Sage has 
>> nothing to offer in this area;
>> it's a module with 5 functions that hasn't seen development since 2009. 
>> Underdeveloped modules like this reflect poorly on the rest of Sage.
>>
>> It's a disservice to learners to offer these facilities of Sage as the 
>> standard vocabulary of doing basic stats on the computer.
>> They will be better off with virtually any other solution: With the 
>> built-in stats module of Python; with Numpy/SciPy; with Pandas; with R.
>>
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/22239d79-cab8-46bd-b6ff-e698441666c9n%40googlegroups.com.


Re: [sage-support] Re: SageMath on Microsoft Windows

2022-02-27 Thread Matthias Koeppe
+1 on adding info on how to install Linux distributions with up-to-date 
binary packages of Sage to our installation guide. 
See https://trac.sagemath.org/ticket/31485

(The updated installation guide, preview at 
https://6212659123a9467b3cb0cd07--sagemath-tobias.netlify.app/installation/index.html
 
already covers WSL but does not mention specific distributions.)

On Sunday, February 27, 2022 at 10:11:40 AM UTC-8 fqgo...@colby.edu wrote:

> I don’t see archlinux in the Microsoft store.
>
> Fernando
>
> On Sun, Feb 27, 2022 at 10:05 AM Dima Pasechnik  wrote:
>
>>
>>
>> On Sun, 27 Feb 2022, 14:37 G. M.-S.,  wrote:
>>
>>>
>>> Thanks, Samuel.
>>>
>>> I think it is a pity there is nothing more straightforward…
>>>
>>> But you will tell me (to look for somebody) to do it.
>>>
>>
>> some Linux distributions have pretty much up to date Sage binary packages.
>>
>> E.g. archlinux has Sage 9.5. Thus, having it installed as WSL2 (cf 
>> https://gist.github.com/ld100/3376435a4bb62ca0906b0cff9de4f94b)   should 
>> be getting you Sage 9.5 quite quickly.
>>
>>
>>
>>> Guillermo
>>>
>>> On Sun, 27 Feb 2022 at 15:28, slelievre  wrote:
>>>
 The Cygwin-based Sage-Windows installer has not been released
 for SageMath 9.4 or SageMath 9.5 yet.

 To get the latest version of Sage running on Windows, one option
 is to activate Windows Subsystem for Linux (also known as WSL),
 select WSL2, and install any Linux distribution there, then follow
 the Linux installation guide.

>>>  
>>>
>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-support...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-support/CANnG188whX6fJTbj1qdPvB-rdeNVm3H_mNmpC3mohE%2B7tM9rMw%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-support...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/CAAWYfq00MjiCDk9Dd8WHDc55%2Bc%3D84PFQLEmyN8VwaD2TiiEVcg%40mail.gmail.com
>>  
>> 
>> .
>>
> -- 
> ==
> Fernando Q. Gouvea  
> Dept of Mathematics and Statistics 
> http://www.colby.edu/~fqgouvea
> Colby College
> Mayflower Hill 5836   
> Waterville, ME 04901  
>
> A training in mathematics is a prerequisite today for work in almost
> any scientific field, but even for those who are not going to become
> scientists, it is essential because, if it is only through speech that
> we can understand what freedom means, only through mathematics 
> can we understand what necessity means.
>   -- W. H. Auden
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c5091c41-9776-4efe-9c6f-321217ed62d0n%40googlegroups.com.


[sage-support] Re: Basic Stats deprecated?

2022-02-26 Thread Matthias Koeppe
On Friday, February 25, 2022 at 10:52:19 AM UTC-8 mat...@gmail.com wrote:

> Will Calculus be deprecated too?
>

See https://trac.sagemath.org/ticket/32260 for the next deprecation 
proposal.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/89d50b73-307a-4a46-ac99-7276acac78e5n%40googlegroups.com.


Re: [sage-support] Re: Basic Stats deprecated?

2022-02-25 Thread Matthias Koeppe
On Friday, February 25, 2022 at 8:32:39 PM UTC-8 wst...@gmail.com wrote:

> Also, if you want to argue that users should explicitly import 
> everything...


No, that's not what I'm arguing. 

The deprecation of the basic_stats module happened because Sage has nothing 
to offer in this area;
it's a module with 5 functions that hasn't seen development since 2009. 
Underdeveloped modules like this reflect poorly on the rest of Sage.

It's a disservice to learners to offer these facilities of Sage as the 
standard vocabulary of doing basic stats on the computer.
They will be better off with virtually any other solution: With the 
built-in stats module of Python; with Numpy/SciPy; with Pandas; with R.




-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/78ff558a-4fa1-44ff-9ff0-aaf1b6eb497dn%40googlegroups.com.


[sage-support] Re: Basic Stats deprecated?

2022-02-25 Thread Matthias Koeppe
If you consider numpy an obscure library, it may be that your syllabus 
needs updating


On Friday, February 25, 2022 at 10:52:19 AM UTC-8 mat...@gmail.com wrote:

> Mean, median and mode are now deprecated. E.g.:
>
> >median([1,2,3])
> 2 :1: DeprecationWarning: sage.stats.basic_stats.median is deprecated; 
> use numpy.median or numpy.nanmedian instead See 
> https://trac.sagemath.org/29662 for details.
>
> But shouldn't these basic functions have some default functionality? Is 
> the intention really to make Sage users call basic functions from 
> libraries. Students (mostly) don't know what numpy is and makes using mean, 
> median and mode weirdly obscure - like calling combinatorics functions in 
> Mathematica. For me (using Sage for classroom teaching) one attraction of 
> Sage is that most basic things that a student would use have names that 
> might be in their textbooks...
>
> Will Calculus be deprecated too?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c7ec42b4-a966-47b6-a538-7bb943a50437n%40googlegroups.com.


Re: [sage-support] Re: Interact broken. SageMath 9.5 on Apple Mac OSX 12.1 . SageMath-9.5_x86_64

2022-02-02 Thread Matthias Koeppe
This looks like https://github.com/jupyter-widgets/ipywidgets/issues/1702 

On Wednesday, February 2, 2022 at 8:33:18 PM UTC-8 Marc Culler wrote:

> That sounds very mysterious.  How can it create widgets if it cannot load 
> the javascript file that implements the widgets?  Maybe the client finds 
> the javascript file in some other path such as usr/local/jupyter and uses 
> that file instead.  Of course a self-contained app cannot rely on anything 
> like that.
>
> - Marc
>
> On Wednesday, February 2, 2022 at 6:59:24 PM UTC-6 Matthias Koeppe wrote:
>
>> On my machine, macOS with Sage 9.5 compiled from source, I see the 404s 
>> too, but the widget from the notebook work anyway. 
>>
>>
>> On Wednesday, February 2, 2022 at 10:03:16 AM UTC-8 Marc Culler wrote:
>>
>>> I figured it out.
>>>
>>> * The root directory for the Tornado web application is 
>>> sage/venv/share/jupyter (determined by trial and error).
>>> * The path component in the url that the jupyter client uses to load the 
>>> widget extension is
>>> /nbextensions/widgets/notebook/js/extension.js
>>> * There is no directory named 
>>> sage/venv/share/jupyter/nbextensions/widgets in the sage 9.5 tree.  Instead
>>> there is a directory named 
>>> sage/venv/share/jupyter/nbextensions/jupyter-js-widgets.
>>>
>>> My fix was to create the directory 
>>> sage/venv/share/jupyter/nbextensions/widgets/notebook
>>> and a symlink sage/venv/share/jupyter/nbextensions/widgets/notebook/js 
>>> -> ../../jupyter-js-widgets
>>>
>>> With that change I get working widgets.  Experiment indicates that the 
>>> jupyter-js-widgets directory
>>> must exist.  But the widgets directory must also exist.  Why does the 
>>> client use a path that does not
>>> exist?  I do not know.  How can it be changed to use the correct path?  
>>> I was not able to figure that
>>> out.  I could not find the code which the client uses to constructs its 
>>> urls.  Maybe it is somewhere
>>> inside a gigantic minimized javascript file.  Who knows?  Files 
>>> containing only one line are not easily
>>> searched with tools like grep.  I guess that is why facebook and twitter 
>>> like them so much.
>>>
>>> - Marc
>>>
>>> On Wednesday, February 2, 2022 at 10:03:18 AM UTC-6 Marc Culler wrote:
>>>
>>>> Never mind.  I must have accidentally tested with 9.4.  Tornado is 
>>>> still returning a 404 when the notebook tries to load 
>>>> /nbextensions/widgets/notebook/js/extension.js.
>>>> On Wednesday, February 2, 2022 at 9:36:10 AM UTC-6 Marc Culler wrote:
>>>>
>>>>> What I said above appears not to be correct.  It looks like enabling 
>>>>> the widgets extension with the instructions in the user_install page did 
>>>>> work.  I am now getting a widget with Sage 9.5.  More testing is needed, 
>>>>> but it looks promising.
>>>>>
>>>>> - Marc
>>>>>
>>>>> On Tuesday, February 1, 2022 at 9:21:23 PM UTC-6 Marc Culler wrote:
>>>>>
>>>>>> No.  I was referring to 
>>>>>> https://ipywidgets.readthedocs.io/en/latest/user_install.html which 
>>>>>> was Samuel's [more details here] link.
>>>>>>
>>>>>> Incidentally, following those instructions did result in a log 
>>>>>> message indicating that the widgets had been enabled in Jupyter.  But 
>>>>>> there 
>>>>>> was no change in the behavior.  Attempting to load extension.js still 
>>>>>> produced a 404.
>>>>>>
>>>>>> - Marc
>>>>>>
>>>>>> On Tue, Feb 1, 2022 at 6:14 PM Matthias Koeppe  
>>>>>> wrote:
>>>>>>
>>>>>>> Marc, are you referring to these instructions?
>>>>>>>
>>>>>>> https://doc.sagemath.org/html/en/installation/launching.html#setting-up-sagemath-as-a-jupyter-kernel-in-an-existing-jupyter-notebook-or-jupyterlab-installation
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, February 1, 2022 at 3:28:48 PM UTC-8 Marc Culler wrote:
>>>>>>>
>>>>>>>> So is Sage following those instructions during its build process?  
>>>>>>>> The docs do not say what those jupyter commands actually do.  They 
>>>>>>>> have 
>

Re: [sage-support] Re: Interact broken. SageMath 9.5 on Apple Mac OSX 12.1 . SageMath-9.5_x86_64

2022-02-02 Thread Matthias Koeppe
On my machine, macOS with Sage 9.5 compiled from source, I see the 404s 
too, but the widget from the notebook work anyway. 


On Wednesday, February 2, 2022 at 10:03:16 AM UTC-8 Marc Culler wrote:

> I figured it out.
>
> * The root directory for the Tornado web application is 
> sage/venv/share/jupyter (determined by trial and error).
> * The path component in the url that the jupyter client uses to load the 
> widget extension is
> /nbextensions/widgets/notebook/js/extension.js
> * There is no directory named sage/venv/share/jupyter/nbextensions/widgets 
> in the sage 9.5 tree.  Instead
> there is a directory named 
> sage/venv/share/jupyter/nbextensions/jupyter-js-widgets.
>
> My fix was to create the directory 
> sage/venv/share/jupyter/nbextensions/widgets/notebook
> and a symlink sage/venv/share/jupyter/nbextensions/widgets/notebook/js -> 
> ../../jupyter-js-widgets
>
> With that change I get working widgets.  Experiment indicates that the 
> jupyter-js-widgets directory
> must exist.  But the widgets directory must also exist.  Why does the 
> client use a path that does not
> exist?  I do not know.  How can it be changed to use the correct path?  I 
> was not able to figure that
> out.  I could not find the code which the client uses to constructs its 
> urls.  Maybe it is somewhere
> inside a gigantic minimized javascript file.  Who knows?  Files containing 
> only one line are not easily
> searched with tools like grep.  I guess that is why facebook and twitter 
> like them so much.
>
> - Marc
>
> On Wednesday, February 2, 2022 at 10:03:18 AM UTC-6 Marc Culler wrote:
>
>> Never mind.  I must have accidentally tested with 9.4.  Tornado is still 
>> returning a 404 when the notebook tries to load 
>> /nbextensions/widgets/notebook/js/extension.js.
>> On Wednesday, February 2, 2022 at 9:36:10 AM UTC-6 Marc Culler wrote:
>>
>>> What I said above appears not to be correct.  It looks like enabling the 
>>> widgets extension with the instructions in the user_install page did work.  
>>> I am now getting a widget with Sage 9.5.  More testing is needed, but it 
>>> looks promising.
>>>
>>> - Marc
>>>
>>> On Tuesday, February 1, 2022 at 9:21:23 PM UTC-6 Marc Culler wrote:
>>>
>>>> No.  I was referring to 
>>>> https://ipywidgets.readthedocs.io/en/latest/user_install.html which 
>>>> was Samuel's [more details here] link.
>>>>
>>>> Incidentally, following those instructions did result in a log message 
>>>> indicating that the widgets had been enabled in Jupyter.  But there was no 
>>>> change in the behavior.  Attempting to load extension.js still produced a 
>>>> 404.
>>>>
>>>> - Marc
>>>>
>>>> On Tue, Feb 1, 2022 at 6:14 PM Matthias Koeppe  
>>>> wrote:
>>>>
>>>>> Marc, are you referring to these instructions?
>>>>>
>>>>> https://doc.sagemath.org/html/en/installation/launching.html#setting-up-sagemath-as-a-jupyter-kernel-in-an-existing-jupyter-notebook-or-jupyterlab-installation
>>>>>
>>>>>
>>>>> On Tuesday, February 1, 2022 at 3:28:48 PM UTC-8 Marc Culler wrote:
>>>>>
>>>>>> So is Sage following those instructions during its build process?  
>>>>>> The docs do not say what those jupyter commands actually do.  They have 
>>>>>> separate instructions for enabling the widgets when using a virtualenv.  
>>>>>> Of 
>>>>>> course Sage's venv is not a true virtualenv as created by venv, so it is 
>>>>>> hard to know whether the virtualenv instruction apply for Sage or not.  
>>>>>> But 
>>>>>> given that the widgets worked before Sage switched to its 
>>>>>> virtualenv-like 
>>>>>> venv I would guess that they do apply.
>>>>>>
>>>>>> It is unclear to me whether this is an issue with the packaging of 
>>>>>> the SageMath app for macOS or whether it is an issue with Sage's build 
>>>>>> process, which I follow when building Sage for the app.  It would be 
>>>>>> helpful to know the meaning of the sentence "Most of the time, 
>>>>>> installing 
>>>>>> ipywidgets automatically configures Jupyter Notebook to use widgets."
>>>>>> Specifically, what does it mean to "configure Jupyter Notebook to use 
>>>>>> widgets".
>>>>>>
>>>>>&

Re: [sage-support] Re: Interact broken. SageMath 9.5 on Apple Mac OSX 12.1 . SageMath-9.5_x86_64

2022-02-01 Thread Matthias Koeppe
On Tuesday, February 1, 2022 at 3:28:48 PM UTC-8 Marc Culler wrote:

> Of course Sage's venv is not a true virtualenv as created by venv,
>

It is actually a true venv, unless no system python can be used and Sage 
builds its own copy of python3.


 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/68d11539-11ba-4eac-aa91-db9926590d42n%40googlegroups.com.


Re: [sage-support] Re: Interact broken. SageMath 9.5 on Apple Mac OSX 12.1 . SageMath-9.5_x86_64

2022-02-01 Thread Matthias Koeppe
Marc, are you referring to these instructions?
https://doc.sagemath.org/html/en/installation/launching.html#setting-up-sagemath-as-a-jupyter-kernel-in-an-existing-jupyter-notebook-or-jupyterlab-installation


On Tuesday, February 1, 2022 at 3:28:48 PM UTC-8 Marc Culler wrote:

> So is Sage following those instructions during its build process?  The 
> docs do not say what those jupyter commands actually do.  They have 
> separate instructions for enabling the widgets when using a virtualenv.  Of 
> course Sage's venv is not a true virtualenv as created by venv, so it is 
> hard to know whether the virtualenv instruction apply for Sage or not.  But 
> given that the widgets worked before Sage switched to its virtualenv-like 
> venv I would guess that they do apply.
>
> It is unclear to me whether this is an issue with the packaging of the 
> SageMath app for macOS or whether it is an issue with Sage's build process, 
> which I follow when building Sage for the app.  It would be helpful to know 
> the meaning of the sentence "Most of the time, installing ipywidgets 
> automatically configures Jupyter Notebook to use widgets."
> Specifically, what does it mean to "configure Jupyter Notebook to use 
> widgets".
>
> - Marc
>
> On Tuesday, February 1, 2022 at 1:26:33 PM UTC-6 slelievre wrote:
>
>> 2022-02-01 15:13:27 UTC, Marc Culler:
>> >
>> > Thanks. And I can reproduce this. I see the error shown below
>> > in the Firefox Console. (I include it here in case anyone might
>> > recognize it).
>>
>>
>> There's an FAQ entry here
>>
>>
>> https://github.com/Wuliyuanulb/ComponentSDKDoc/blob/bfe53cf2162f62134356b58d7eae07e367044602/_build/_sources/faq.md.txt
>>
>> that reads
>>
>> > In browser F12 window, there is `Couldn't process kernel message`
>> > error in Console log. WrappedError message will be like:
>> > ```
>> > Error: Class jupyter.widget not found in registry at http://xxx
>> > ```
>> > This is because ipywidgets not correctly enabled in jupyter extension
>> > when using pip to install. Reinstall using conda will solve this issue.
>> > See [more details here](
>> https://ipywidgets.readthedocs.io/en/latest/user_install.html).
>> > ```
>> > conda install -c conda-forge ipywidgets
>> > ```
>>
>> And here are some more related discussions,
>> hoping there's something relevant to dig from them.
>>
>> https://github.com/Caltech-IPAC/firefly_widgets/issues/6
>> https://github.com/InsightSoftwareConsortium/itkwidgets/issues/207
>>
>> https://github.com/ipython-contrib/jupyter_contrib_nbextensions/issues/1319
>> https://github.com/jupyter-widgets/ipywidgets/issues/2569
>> https://github.com/jupyter-widgets/ipywidgets/issues/377
>> https://github.com/jupyterlab/jupyterlab/issues/4398
>> https://github.com/maartenbreddels/ipyvolume/issues/36
>> https://github.com/OpenGeoscience/geonotebook/pull/51
>> https://github.com/twosigma/beakerx/issues/6582
>>
>> Found by searching using this request
>>
>>
>> https://github.com/search?q=Class+jupyter.widget+not+found+in+registry=issues
>>
>> Not sure that helps at all, sorry.  --Samuel
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/26b228ed-ed16-400b-849c-7c3be030a413n%40googlegroups.com.


[sage-support] Re: Sage crash report

2021-12-09 Thread Matthias Koeppe
"make sagelib-clean" will fix this

On Thursday, December 9, 2021 at 12:18:02 PM UTC-8 Emmanuel Charpentier 
wrote:

> A recent upgrade of Debian testing seems to have broken Sage, which does 
> not find libgsl.so.25 Crash report attached.
>
> An attempt at make -b also fails (see attached install.log).
>
> The worse is :
>
> charpent@zen-book-flip:/usr/local/sage-9$ locate libgsl.so
>
> /usr/lib/x86_64-linux-gnu/libgsl.so
>
> /usr/lib/x86_64-linux-gnu/libgsl.so.25
>
> /usr/lib/x86_64-linux-gnu/libgsl.so.25.0.0
>
> charpent@zen-book-flip:/usr/local/sage-9$ dpkg -l "*libgsl*"
>
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
>
> | 
> État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=att>
>
> |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
>
> ||/ NomVersion  Architecture Description
>
> +++-==---==>
>
> ii  libgsl-dev 2.7.1+dfsg-3 amd64GNU Scientific Library (GSL) 
> ->
>
> un  libgsl0  (aucune description n'est 
> disp>
>
> un  libgsl0-dev  (aucune description n'est 
> disp>
>
> un  libgsl0ldbl  (aucune description n'est 
> disp>
>
> un  libgsl2  (aucune description n'est 
> disp>
>
> un  libgsl23 (aucune description n'est 
> disp>
>
> ii  libgsl27:amd64 2.7.1+dfsg-3 amd64GNU Scientific Library (GSL) 
> ->
>
> ii  libgslcblas0:amd64 2.7.1+dfsg-3 amd64GNU Scientific Library (GSL) 
> ->
>
>
> I'm a bit at loss...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/a250b849-5ff2-4298-be15-4238fad2e560n%40googlegroups.com.


Re: Fwd: [sage-support] Sage 9.3 for Windows crashing

2021-09-23 Thread Matthias Koeppe
No, the 9.4 binaries have the same problem, as noted 
in 
https://wiki.sagemath.org/ReleaseTours/sage-9.4#Availability_as_binaries_and_in_distributions

We have two tickets in the 9.5 development series that aim to fix this 
problem:
- https://trac.sagemath.org/ticket/32424 (waiting for review)
- https://trac.sagemath.org/ticket/32488 (which will be in 9.5.beta2)



On Thursday, September 23, 2021 at 2:49:40 AM UTC-7 Dima Pasechnik wrote:

> On Wed, Sep 22, 2021 at 10:12 PM Fernando Gouvea  
> wrote:
>
>> Update: the problem is machine-dependent. On one Dell laptop, plot works 
>> with no problem. On a different one, big crash.
>>
>
> We see this with other operating systems, too. Hopefully fixed in 9.4, see
> https://trac.sagemath.org/ticket/31565
>  
>
>> Fernando
>> On 9/22/2021 3:49 PM, William Stein wrote:
>>
>> -- Forwarded message -
>> From: Fernando Q. Gouvea 
>> Date: Wed, Sep 22, 2021 at 12:26 PM
>> Subject: Re: [sage-support] Sage 9.3 for Windows crashing
>> To: William Stein 
>>
>>
>> At this point, only plotting has caused the problem. For example:
>>
>> sage: K=Qp(7)
>> sage: K
>> 7-adic Field with capped relative precision 20
>> sage: a=K(8)
>> sage: a
>> 1 + 7 + O(7^20)
>> sage: sqrt(a)
>> 1 + 4*7 + 2*7^2 + 7^3 + 3*7^4 + 2*7^5 + 4*7^6 + 2*7^7 + 5*7^8 + 7^11 +
>> 4*7^12 + 4*7^13 + 6*7^14 + 2*7^15 + 4*7^16 + 4*7^17 + 5*7^18 + O(7^20)
>> sage: log(a)
>> 7 + 3*7^2 + 7^3 + 6*7^4 + 5*7^5 + 2*7^6 + 7^7 + 5*7^8 + 4*7^9 + 4*7^10 +
>> 2*7^11 + 5*7^12 + 7^13 + 5*7^14 + 6*7^15 + 2*7^16 + 2*7^17 + 2*7^18 +
>> 7^19 + O(7^20)
>>
>> That all works fine.
>>
>> Fernando
>>
>> On 9/22/2021 2:46 PM, William Stein wrote:
>>
>> On Wed, Sep 22, 2021 at 11:36 AM Fernando Q. Gouvea  
>> wrote:
>>
>> I just had SageMath 9.2 crash, so I tried installing 9.3. Alas, I get the 
>> same problem. The offending command is pretty innocuous:
>>
>> sage: plot(ln(1+x),(-1,5))
>>
>> The Sage window then crashes. In the notebook I get a message that the 
>> kernel just died. Running it in the Sage Terminal, sage crashes and leaves 
>> this message behind:
>>
>> 
>> 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.3/src/bin/sage-python: line 2:  1535 Segmentation fault  
>> (core dumped) sage -python "$@"
>>
>> Any ideas as to what is going on?
>>
>> Do lots of things you try cause problems like this or is it just plotting?
>>
>> E.g., what if you do some basic arithmetic with p-adic numbers, e.g.,
>> some examples from here:
>> https://doc.sagemath.org/html/en/reference/padics/sage/rings/padics/tutorial.html
>>
>> (Sorry, I can't help asking that given that I learned all about
>> p-adics from your book decades ago...)
>>
>>
>> Fernando
>>
>>
>> --
>> ==
>> Fernando Q. Gouvea
>> Carter Professor of Mathematics
>> Colby College
>> Mayflower Hill 5836
>> Waterville, ME 04901fqgo...@colby.edu   http://www.colby.edu/~fqgouvea
>>
>> Humility engenders learning because it beats back the arrogance
>> that puts blinders on. It leaves you open for truths to reveal
>> themselves. You don't stand in your own way.
>>-- Wynton Marsalis
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-support...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/e587c471-9ffa-4364-5fa2-fbf40d63e7d6%40colby.edu.
>>
>> --
>> ==
>> Fernando Q. Gouvea
>> Carter Professor of Mathematics
>> Colby College
>> Mayflower Hill 5836
>> Waterville, ME 04901fqgo...@colby.edu http://www.colby.edu/~fqgouvea
>>
>> What garlic is to food, insanity is to art.
>>
>>
>>
>>
>> -- 
>> =
>> Fernando Q. Gouvea http://www.colby.edu/~fqgouvea
>> Carter Professor of Mathematics
>> Dept. of Mathematics and Statistics
>> Colby College  
>> 5836 Mayflower Hill
>> Waterville, ME 04901   
>>
>> We receive the deepest truths only when we're patient enough
>> -- and stable enough and docile enough -- to allow ourselves
>> to be taught them.
>>   -- R. R. Reno, in "Piety's Rightful Claim"
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-support...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> 

[sage-support] Re: No module named 'sage.all_cmdline'

2021-09-14 Thread Matthias Koeppe
Report Ubuntu packaging bugs to Ubuntu.


On Tuesday, September 14, 2021 at 10:50:56 AM UTC-7 mob...@gmail.com wrote:

> I installed *"Sage"* on *Google Colab*
> https://askubuntu.com/a/1159008/1033768  
>
> *via the command:  *
>
> !sudo apt-get install build-essential m4 dpkg-dev
> !sudo apt-get update 
> !sudo apt-get install sagemath
>
> *I get the error:*  
>
>   File "script.py", line 11, in 
> from sage.all_cmdline import *   
> ModuleNotFoundError: No module named 'sage.all_cmdline'
>
> Google Colab works on
> Description: Ubuntu 18.04.5 LTS
> Codename: bionic
> model name: AMD EPYC 7B12
>
>
> Why can't I install *"Sage"* ? What could be the reasons for this error?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/40da8d16-4718-4365-9786-4d1411884b46n%40googlegroups.com.


[sage-support] Re: about Sage 9.3

2021-09-09 Thread Matthias Koeppe
This is a known issue with the binary distributions for Sage 9.3 and 9.4. 
See 
https://wiki.sagemath.org/ReleaseTours/sage-9.4#Availability_as_binaries_and_in_distributions
Install from source instead.

On Thursday, September 9, 2021 at 8:01:00 AM UTC-7 GÖKHAN SOYDAN wrote:

> hello everybody,
> I first installed Sage 9.4 on my IMac (Catalina 10.15.7).
> It was running, but some old codes did not run. (I know these codes are 
> working on another computer which has Sage 9.3.) After deleting all Sage 
> installation documents, 
> I installed Sage 9.3, but Sage 9.3 did not work. On my screen, the 
> following message seems:
>
> │ SageMath version 9.3, Release Date: 2021-05-09 │
>
> │ Using Python 3.9.2. Type "help()" for help.│
>
> └┘
>
> 
>
> (no backtrace available)
>
> 
>
> Unhandled SIGILL: An illegal instruction 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.
>
> 
>
> Illegal instruction: 4
>
> logout
>
> Saving session...
>
> ...copying shared history...
>
> ...saving history...truncating history files...
>
> ...completed.
>
> ===
>
> Can someone help me? What should I do to use Sage 9.3?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/04655f1a-dbe8-427f-a26e-9f1e2adda5e2n%40googlegroups.com.


[sage-support] Re: Function-call syntax deprecation

2021-09-09 Thread Matthias Koeppe
Instead of:
gamma=vector([t,t^2,t^3])
use:
gamma=vector([t,t^2,t^3]).function(t)

Alternatively, keep gamma as is and use gamma(t=x) instead of gamma(x).

On Thursday, September 9, 2021 at 1:18:52 PM UTC-7 Federico Galetto wrote:

> Hello, I get a warning due to function-call syntax deprecation and I don't 
> understand how to fix it despite looking at other similar conversations.
>
> Here is the setup for my code:
>
> t=var('t')
> gamma=vector([t,t^2,t^3])
> curve=parametric_plot(gamma,(t,-2,2),color='black',radius=0.02)
> v=derivative(gamma,t)
> T=v/v.norm()
> Tp=derivative(T,t)
> N=Tp/Tp.norm()
> B=T.cross_product(N)
>
> This code creates the plot of a space curve and computes T,N,B which are 
> unit tangent, normal, and binormal vectors. Now I want to create an 
> interactive 3d plot:
>
> def frame(x):
> pT = T(x).plot(start=gamma(x),radius=0.02)
> pN = N(x).plot(color='red',start=gamma(x),radius=0.02)
> pB = B(x).plot(color='green',start=gamma(x),radius=0.02)
> frenet = pT + pN + pB
> whole = frenet + curve
> return whole
> a = animate([frame(x) for x in srange(-0.5,1.5,.02)])
> a.show()
>
> Although this works, I get the syntax deprecation warning at the line 'a = 
> animate(...'.
>
> Any help is greatly appreciated!
> Fred
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/59eba31c-57f2-4c9b-851a-335526ee2dc6n%40googlegroups.com.


[sage-support] Re: Sage 9.4 crashes with Debian 11

2021-09-05 Thread Matthias Koeppe
Installed the binary distribution? Known to fail with some processors 
(https://trac.sagemath.org/ticket/32424).
Try installing from source instead.

On Sunday, September 5, 2021 at 8:22:16 AM UTC-7 Topaze wrote:

> Hello.
>
> A quick recapitulation of my historic :
>
> Debian 10 + Sagemath 9.2 : OK (everything works fine).
> Debian 10 + Sagemath 9.3 : Crash (systematic).
>
> In between, I made a full distribution upgrade.
>
> Debian 11 + Sagemath 9.4 : Crash.
>
> Then I reverted to an older version, just to check.
>
> Debian 11 + Sagemath 9.2 : OK.
>
> I'm reporting here for the figure case  : Debian 11 + Sagemath 9.4 
> (2021-08-22).
> My processor is an AMD Sempron 3850 APU with Radeon R3
>
> The error messages are joined in the log file.
>
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/865f57f2-6651-4e2a-b0a0-9aa8ed1b4ca3n%40googlegroups.com.


[sage-support] Re: Sage 9.4_20.04 Ubuntu: error relocate-once.py

2021-09-03 Thread Matthias Koeppe
Thanks, I've noted this 
in 
https://wiki.sagemath.org/ReleaseTours/sage-9.4#Availability_as_binaries_and_in_distributions

On Friday, September 3, 2021 at 3:02:47 AM UTC-7 Rolandb wrote:

> Hi,
>
> Running the file 'relocate-once.py', I got an error: directory 'python' 
> not recognized.
> Changing the line #!.. python into #!.. python3 solved the problem.
>
> Roland  
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/1c7a5fd0-4ef5-4f66-a80c-04007ce3bf52n%40googlegroups.com.


Re: [sage-support] Sage Crash Report

2021-09-01 Thread Matthias Koeppe
See 
https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source
point 4 ("./configure --prefix")

On Wednesday, September 1, 2021 at 12:00:15 PM UTC-7 hbetx9 wrote:

> So I got this working in my home directory but want the SageMath directory 
> system wide. I moved it to /opt and changed ownership to root.root, however 
> this causes now a disagreement with the SAGE_ROOT environment variable. 
> Should I unpack the tarball as root there to install or is there an easy 
> config/make that I can run on this directory to get it to work as a system 
> wide install?
>
> On Tuesday, August 31, 2021 at 4:22:10 PM UTC-5 Matthias Koeppe wrote:
>
>> On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote:
>>
>>> On my system, python2 and python3 is installed, but there is no generic 
>>> python symlink. Does this need to be created for sage and if so should it 
>>> be python3? In installed from tarball, so this is not an issue with the 
>>> Ubuntu package.
>>
>>
>> The latest binary for Linux (https://www.sagemath.org/download.html) is 
>> Sage 9.3. If you are using this binary tarball, you will have to make sure 
>> that the symlink python->python3 exists; there is a package that provides 
>> it. See also 
>> https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries
>>
>> The latest version is Sage 9.4. Using the source tarball, there is no 
>> need to do anything about python/python3. Just follow the instructions in 
>> the README. 
>>
>>  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b8a59d1a-9c4a-4715-8ae6-f2df0a6c4877n%40googlegroups.com.


Re: [sage-support] Sage Crash Report

2021-08-31 Thread Matthias Koeppe
On Tuesday, August 31, 2021 at 12:55:46 PM UTC-7 hbetx9 wrote:

> On my system, python2 and python3 is installed, but there is no generic 
> python symlink. Does this need to be created for sage and if so should it 
> be python3? In installed from tarball, so this is not an issue with the 
> Ubuntu package.


The latest binary for Linux (https://www.sagemath.org/download.html) is 
Sage 9.3. If you are using this binary tarball, you will have to make sure 
that the symlink python->python3 exists; there is a package that provides 
it. See 
also 
https://wiki.sagemath.org/ReleaseTours/sage-9.3#Availability_in_distributions_and_as_binaries

The latest version is Sage 9.4. Using the source tarball, there is no need 
to do anything about python/python3. Just follow the instructions in the 
README. 

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/a16547b7-1dd7-4c5d-97fa-2e231cd702adn%40googlegroups.com.


Re: [sage-support] Re: after upgrade to 9.3, SignalError: Illegal instruction

2021-08-25 Thread Matthias Koeppe
I've opened https://trac.sagemath.org/ticket/32424 for this issue with Sage 
9.4.


On Wednesday, August 25, 2021 at 8:15:02 PM UTC-7 wst...@gmail.com wrote:

> Hi,
>
> I release cocalc-docker ([1], [2]) a few days ago with sage-9.4, and had 
> people reporting back "illegal instruction" issues.  Sage is built there 
> with SAGE_FAT_BINARY="yes", using this script [3].  One person who reported 
> a problem had a "Dell PowerEdge R710." and I built on an intel Dell 
> PowerEdge R630, for what it is worth.  They got the error "An illegal 
> instructor occurred" when computing "5+2" in Sage. 
>
> My solution for now is to keep cocalc-docker at sage-9.3 for the time 
> being, and suggest that people build sage from source on their own machine 
> if necessary.   I'll let you know if I have any further information, but I 
> just wanted to add this data point.
>
> [1] https://github.com/sagemathinc/cocalc-docker
> [2] https://hub.docker.com/r/sagemathinc/cocalc
> [3] 
> https://github.com/sagemathinc/cocalc-docker/blob/master/scripts/install_sage.sh
>
> On Wednesday, August 25, 2021 at 8:57:44 AM UTC-7 Marco Streng wrote:
>
>> In the end I build 9.4 from source and that worked perfectly. And it 
>> turned out that the Ubuntu 18.04 binaries of 9.2 also work on this 
>> particular machine (though we went for 9.4 in the end). Thanks again for 
>> the help.
>>
>> Op dinsdag 24 augustus 2021 om 18:03:01 UTC+2 schreef slelievre:
>>
>>> 2021-08-24 05:48 UTC, Dima Pasechnik: 
>>> > 
>>> > These "illegal instruction" errors are an indication 
>>> > that the binary was built for a more advanced CPU 
>>> > than yours - which does not support certain CPU 
>>> > commands. It's a bug in "fat binary" build process 
>>> > we see for some time. 
>>> > 
>>> > Build Sage yourself, or use Conda. 
>>>
>>> I opened a ticket at binary-pkg for that: 
>>> https://github.com/sagemath/binary-pkg/issues/31 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/5f3adbcd-2354-4e5e-b110-0a98622cde7dn%40googlegroups.com.


[sage-support] Re: Does anyone know what this means?

2021-08-01 Thread Matthias Koeppe
The update to this (and other IPython/Jupyter tickets) is 
in https://trac.sagemath.org/ticket/31280 -- which needs help.

On Tuesday, July 27, 2021 at 8:13:29 AM UTC-7 David Lowry-Duda wrote:

> This comes from python-prompt-toolkit. See here: 
> https://github.com/prompt-toolkit/python-prompt-toolkit/pull/1291
>
> This was fixed in python-prompt-toolkit in December, I think in version 
> 3.0.9. Sage is currently using 3.0.5. When we update to use a more recent 
> version of python-prompt-toolkit, I think this should go away.
>
> - DLD
>
> On Tuesday, July 27, 2021 at 10:15:06 AM UTC-4 John Cremona wrote:
>
>> At the end of a run of some code I have run before, without seeing this: 
>>
>> /usr/local/sage/sage-9.3/local/lib/python3.9/site-packages/prompt_toolkit/renderer.py:514:
>>  
>>
>> DeprecationWarning: The explicit passing of coroutine objec 
>> ts to asyncio.wait() is deprecated since Python 3.8, and scheduled for 
>> removal in Python 3.11. 
>> await wait(coroutines, return_when=FIRST_COMPLETED) 
>>
>> This is sage-9.3 on ubuntu. I assume that I can ignore it. 
>>
>> John 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/40b49d3c-e7cf-4a4c-9bfe-33c33ba3bda8n%40googlegroups.com.


[sage-support] Re: What can I do to get sage not to compile numpy?

2021-07-17 Thread Matthias Koeppe
On Saturday, July 17, 2021 at 7:41:16 PM UTC-7 bluf...@gmail.com wrote:

> Using dnf to install sagemath works on Fedora 34,  but then /usr/bin/sage 
> gives
> a weird error message.  
>

Please report Fedora packaging bugs to Fedora.
 

> Compiling sage from sage-9.2.tar.gz does not work.
> Using CC=clang CXX=clang++ FC=flang it hangs.  Here are the last three
> lines that get printed to the screen:
>
> [numpy-1.19.5] creating build/src.linux-x86_64-3.9/numpy
> [numpy-1.19.5] creating build/src.linux-x86_64-3.9/numpy/distutils
> [numpy-1.19.5] building library "npymath" sources
>

This is much too little information. We need at least the top-level 
config.log, and the full build log of the package.

In any case, 9.2 is outdated, but also 9.3 does not support building on 
Fedora 34 with the default compilers.
You can try the branch at https://trac.sagemath.org/ticket/31786
 

> What can I do to get sage not to compile numpy?
>

This is not supported by the Sage distribution.


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b2302361-6011-4833-bf10-95274db9c67dn%40googlegroups.com.


[sage-support] Re: polyhedra with strict inequalities and Ehrhart

2021-07-07 Thread Matthias Koeppe
On Wednesday, July 7, 2021 at 2:36:27 PM UTC-7 kcrisman wrote:

> Normaliz already supports half-open polyhedra, see section 3.12 ("open 
>> facets") in the Normaliz manual
>> see https://github.com/Normaliz/Normaliz/blob/master/doc/Normaliz.pdf
>>
>
> Thank you!  But, based on the tickets I've just been cc:ed on, probably 
> there is no current easy Sage interface for these?  
>

That's right. You would have to use PyNormaliz directly.

Also, it's only certain of the inequalities I would want to be strict - is 
> that too much to ask?  Maybe "Semiopen polyhedra" is more like what I'm 
> looking for - I do not know the facets, only the inequalities, which in 
> more complicated examples than the one I provided tend to have nontrivial 
> interactions.
>

I think Normaliz only supports the special case of polyhedra with some 
facets removed, not the more general situation in which you would remove 
some lower-dimensional faces. This case would still have to be handled 
using a combination of techniques, including inclusion-exclusion and 
reciprocity (including the technique of "inside out polytopes").

sage.geometry.polyhedron.modules.FormalPolyhedraModule is a step toward 
expressing such decomposition and transformation techniques, 
see https://trac.sagemath.org/ticket/29799


 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b231ea8f-e636-4d51-bbf7-f3e7bce4f328n%40googlegroups.com.


[sage-support] Re: polyhedra with strict inequalities and Ehrhart

2021-07-07 Thread Matthias Koeppe
Normaliz already supports half-open polyhedra, see section 3.12 ("open 
facets") in the Normaliz manual
see https://github.com/Normaliz/Normaliz/blob/master/doc/Normaliz.pdf



On Wednesday, July 7, 2021 at 1:26:01 PM UTC-7 kcrisman wrote:

> Thanks to the MUCH easier install now of things like pynormaliz and latte 
> (thanks to all who worked on those!), I can now do the following and 
> related computations nicely.  
>
> sage: n=1 
>   
> sage: P = 
> Polyhedron(ieqs=[[-(n)/2,1,0,0],[-(n)/2,0,1,0],[(3*n)/2,-1,-1,-1],[0,1
> : 
> ,0,0],[0,0,1,0],[0,0,0,1],[n,-1,0,0],[n,0,-1,0],[n,0,0,-1]],backend='norma
> : liz')   
>   
> sage: [p.factor() for p in P.ehrhart_quasipolynomial()]   
>   
> [(1/48) * (t + 2) * (t + 4) * (t + 6), (1/48) * (t - 1) * (t + 1) * (t + 
> 3)]
>
> However, what I really need is an Ehrhart quasi-polynomial for some of the 
> above inequalities to be *strict* inequalities, and I'm not sure how to do 
> that without tedious finding of some (not all) faces and subtracting them 
> off (which could be a nightmare and/or wrong in any case).  Unfortunately 
> changing the non-strict inequalities "by hand" to other numbers gives the 
> wrong answers (really unsurprising, since it's a different polytope).
>
> Any thoughts?  Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/a468b8bd-3f11-4418-92fc-4f9247ebc1d0n%40googlegroups.com.


[sage-support] Re: error building sage-9.3 from source

2021-05-19 Thread Matthias Koeppe
We'd need to see the top-level config.log corresponding to a failing build.


On Wednesday, May 19, 2021 at 3:37:42 PM UTC-7 Greg Marks wrote:

> > On a Debian 10 system, building sage-9.3 from source fails with this
> > error:
> > 
> > ...
> > [dochtml] Traceback (most recent call last):
> > [dochtml] File "/usr/lib/python3.7/runpy.py", line 183, in 
> _run_module_as_main
> > [dochtml] mod_name, mod_spec, code = _get_module_details(mod_name, 
> _Error)
> > [dochtml] File "/usr/lib/python3.7/runpy.py", line 142, in 
> _get_module_details
> > [dochtml] return _get_module_details(pkg_main_name, error)
> > [dochtml] File "/usr/lib/python3.7/runpy.py", line 109, in 
> _get_module_details
> > [dochtml] __import__(pkg_name)
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage_docbuild/__init__.py",
>  
> line 57, in 
> > [dochtml] import sage.all
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/all.py",
>  
> line 142, in 
> > [dochtml] from sage.rings.all import *
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/all.py",
>  
> line 50, in 
> > [dochtml] from .finite_rings.all import *
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/finite_rings/all.py",
>  
> line 21, in 
> > [dochtml] from .finite_field_constructor import FiniteField
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/finite_rings/finite_field_constructor.py",
>  
> line 182, in 
> > [dochtml] from .finite_field_givaro import FiniteField_givaro
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/finite_rings/finite_field_givaro.py",
>  
> line 24, in 
> > [dochtml] from sage.rings.finite_rings.element_givaro import Cache_givaro
> > [dochtml] File "sage/rings/finite_rings/element_givaro.pyx", line 1, in 
> init sage.rings.finite_rings.element_givaro 
> (build/cythonized/sage/rings/finite_rings/element_givaro.cpp:20735)
> > [dochtml] File "sage/rings/finite_rings/element_pari_ffelt.pyx", line 
> 35, in init sage.rings.finite_rings.element_pari_ffelt 
> (build/cythonized/sage/rings/finite_rings/element_pari_ffelt.c:14998)
> > [dochtml] File "sage/rings/polynomial/polynomial_element.pyx", line 67, 
> in init sage.rings.polynomial.polynomial_element 
> (build/cythonized/sage/rings/polynomial/polynomial_element.c:106651)
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/polynomial/polynomial_ring.py",
>  
> line 154, in 
> > [dochtml] import sage.rings.polynomial.polynomial_element_generic as 
> polynomial_element_generic
> > [dochtml] File 
> "/usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/polynomial/polynomial_element_generic.py",
>  
> line 1533, in 
> > [dochtml] from sage.rings.polynomial.polynomial_rational_flint import 
> Polynomial_rational_flint
> > [dochtml] ImportError: 
> /usr/local/Math_Software/sage-9.3/local/lib/python3.7/site-packages/sage/rings/polynomial/
> polynomial_rational_flint.cpython-37m-x86_64-linux-gnu.so: undefined 
> symbol: _Z27_arb_fmpz_poly_evaluate_arbP10arb_structPKllPKS_l
> > make[3]: *** [Makefile:2280: doc-html] Error 1
> > make[2]: *** [Makefile:2160: all-start] Error 2
> > make[2]: Leaving directory '/usr/local/Math_Software/sage-9.3/build/make'
> > 
> > I've tried it both with "./configure --with-system-flint=no" and with
> > "./configure --with-system-arb=no" and with a simple "./configure";
> > same problem each way.
> > 
> > Best regards,
> > Greg Marks
>
> For the record, this problem was solved by starting the build with
> "./configure --with-system-python3=no"; then "make" completes without
> error and "make ptestlong" shows all sage-9.3 tests passed.
>
> Best regards,
> Greg Marks
>
> P.S. On some machines with Python 3.7.3 installed, the problem described
> above arises; on others it doesn't. I suspect the problem has something
> to do with the specific Python packages installed and is possibly
> related to the (currently unanswered) question posed here:
>
>
> https://stackoverflow.com/questions/67117097/c-cpython-38-x86-64-linux-gnu-so-undefined-symbol-zn6caffe28typemeta21-typem
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b2f80184-19bd-47cb-8313-027035da3501n%40googlegroups.com.


[sage-support] Re: Trouble understanding `sage -optional` answer

2021-05-04 Thread Matthias Koeppe
On Tuesday, May 4, 2021 at 7:00:55 AM UTC-7 Emmanuel Charpentier wrote:

> Trying to list the installed optional packages, I innocently typed :
>
> charpent@zen-book-flip:~$ sage -optional | grep -v not_instal
>
> The answer left me stimyed :
>
> /usr/local/sage-9/local/lib/python3.9/site-packages/sage/misc/package.py:114: 
> UserWarning: failed to fetch the version of pkg='ore_algebra' at 
> https://pypi.org/pypi/ore_algebra/json
>   warnings.warn("failed to fetch the version of pkg={!r} at {}".format(pkg, 
> url))
>
> This, I understand as the impossibility of reaching the repository of 
> ore-package
>
"sage-optional" uses PyPI to determine available versions of pip packages 
(see 
https://doc.sagemath.org/html/en/developer/packaging.html#package-source-types 
for the definition). 

The ore-algebra project, unfortunately, does not make proper releases; the 
Sage package is keyed to a particular commit in the project's github.

$ cat build/pkgs/ore_algebra/requirements.txt 
git+https://github.com/mkauers/ore_algebra@6826ac49b4cdf66a563449aced21a2fd1fd085c9#egg=ore_algebra
You can help by convincing the project maintainers to follow the best 
practices for Python packages: making releases and publishing them on PyPI.

[package]...[latest version] ([version])
>
> cmdstanpy...? (0.9.75)
> cypari2.? (2.1.2)
> dot2tex.2.11.3.p0 (2.11.3.p0)
> fricas..1.3.6 (1.3.6)
> gap_jupyter.0.9 (0.9)
> gap_packages4.11.0.p1 (4.11.0.p1)
> json5...? (0.9.5)
> jupyter_kernel_gap..? (0.9)
> jupyter_kernel_singular.? (0.9.7)
> jupyterlab..3.0.9 (2.2.9)
> jupyterlab_server...? (1.2.0)
> kenzo...1.1.9 (1.1.9)
> libsemigroups...1.0.9 (1.0.9)
> pandas..? (1.2.3)
> pysingular..0.9.7 (0.9.7)
> python_dateutil.? (2.8.1)
> sagemath_standard...? (9.3rc5)
> singular_jupyter0.9.7 (0.9.7)
> tqdm? (4.59.0)
> ujson...? (4.0.2)
>
> Some of these results are marked ? as available versions ; this, I 
> interpret as Python packages installed viapip(either by me (e. g.cmdstanpy`) 
> or by another installer).
>
> jupyterlab installed version is 2.2.9, whereas the available version is 
> 3.0.9.why hasn’t it upgraded during the last Sage upgrade ?
>
Our jupyterlab package, added in https://trac.sagemath.org/ticket/26059, is 
a pip package. It uses the following version specification: 

$ cat build/pkgs/jupyterlab/requirements.txt 
jupyterlab ~= 2.2.5 
I would hope that in the Sage 9.4 series, we can upgrade 
ipython/jupyter/jupyterlab. There is already a ticket for this 
task: https://trac.sagemath.org/ticket/31280 – help is welcome.


 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/9293264f-d52c-4ccc-9767-7b6caca19d75n%40googlegroups.com.


Re: [sage-support] problem compiling sage 9.2 on RHEL 6

2021-03-07 Thread Matthias Koeppe
>From numpy.log:

gcc: numpy/core/src/multiarray/flagsobject.c
gcc: numpy/core/src/multiarray/nditer_api.c
In file included from 
/net/dlp762/share/application-software/Gcc/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/immintrin.h:51,
 from numpy/core/src/umath/simd.inc.src:25,
 from numpy/core/src/umath/loops.c.src:50:
/net/dlp762/share/application-software/Gcc/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/avxintrin.h:1194:1:
 
error: inlining failed in call to always_inline '_mm256_movemask_ps': 
target specific option mismatch

Try upgrading your compiler.




On Saturday, March 6, 2021 at 10:35:39 AM UTC-8 
klaus.ha...@ruhr-uni-bochum.de wrote:

> High,
>
> I did a fresh start over:
>
> cd sage-9.2
> make distclean
> ./configure --with-mp=gmp
> make mpir-clean
> make bzip2 xz pcre -j3
> make -j8
>
> But compilation still fails for numpy-1.19.1.
> I include config.log and error log.
>
> Regards, Klaus Hackenberg
>
> --
> Klaus Hackenberg
> IT-Systeme und Software-Integration
> IT.SERVICES
> Ruhr-Universität Bochum | 44780 Bochum
> fon: +49 234 32 23485 <+49%20234%203223485>
> http://www.it-services.rub.de/
>
> -Ursprüngliche Nachricht-
> Von: sage-s...@googlegroups.com  Im Auftrag 
> von Dima Pasechnik
> Gesendet: Samstag, 6. März 2021 16:13
> An: sage-support 
> Betreff: Re: [sage-support] problem compiling sage 9.2 on RHEL 6
>
> On Sat, Mar 6, 2021 at 10:36 AM Dima Pasechnik  wrote:
> >
> > why did you run ./configure with the option "--with-blas=openblas" ?
> >
> > Please try re-running ./configure without it.
> >
> > Then hopefully numpy etc will be built.
>
> Sorry, that was wrong.
>
> It's probably your new Python interfering.
> Start from scratch
>
> make distclean
> ./configure --with-mp=gmp
>
> I suppose it will pick up your newly installed Python3 and use it, you can 
> check config.log for this, or just the output of ./configure
>
>
> >
> >
> >
> > On Sat, 6 Mar 2021, 09:55 'Hackenberg, Klaus' via sage-support, <
> sage-s...@googlegroups.com> wrote:
> >>
> >> High,
> >>
> >> running "make toolchain shows only
> >>
> >> [lsf@dlp762 sage-9.2]$ make toolchain make build/make/Makefile --stop
> >> make[1]: Entering directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2'
> >> make[1]: `build/make/Makefile' is up to date.
> >> make[1]: Leaving directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2'
> >> build/bin/sage-logger \
> >> "cd build/make && ./install 'toolchain'" 
> >> logs/install.log
> >> make[1]: Entering directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2/build/make'
> >> make[1]: Leaving directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2/build/make'
> >> Nothing to (re)build / all up-to-date.
> >> [lsf@dlp762 sage-9.2]$
> >>
> >> I include the config log.
> >>
> >> Regards, Klaus Hackenberg
> >>
> >> --
> >> Klaus Hackenberg
> >> IT-Systeme und Software-Integration
> >> IT.SERVICES
> >> Ruhr-Universität Bochum | 44780 Bochum
> >> fon: +49 234 32 23485 <+49%20234%203223485>
> >> http://www.it-services.rub.de/
> >>
> >> -Ursprüngliche Nachricht-
> >> Von: sage-s...@googlegroups.com  Im 
> >> Auftrag von Dima Pasechnik
> >> Gesendet: Samstag, 6. März 2021 01:08
> >> An: sage-support ; Matthias Koeppe 
> >> 
> >> Betreff: Re: [sage-support] problem compiling sage 9.2 on RHEL 6
> >>
> >> "Error building wheel for numpy"
> >>
> >> please post
> >> /net/dlp762/share/application-software/Sage/sage-9.2/config.log
> >>
> >> could you also please try running
> >>
> >> make toolchain
> >>
> >> and then run make.
> >>
> >>
> >>
> >> Matthias,
> >> is it another instance of not having .pc files ready for blas/lapack 
> etc?
> >>
> >> Running from numpy source directory.
> >> 
> /net/dlp762/share/application-software/Sage/sage-9.2/local/var/tmp/sage/build/numpy-1.19.1/src/numpy/distutils/system_info.py:1914:
> >> UserWarning:
> >> Optimized (vendor) Blas libraries are not found.
> >> Falls back to netlib Blas library which has worse performance.
> >> A better performance should be easily gained by switching
> >> Blas library.
> >> if self._calc_info(blas):
> >> 
> /net/dlp762/sha

Re: [sage-support] problem compiling sage 9.2 on RHEL 6

2021-03-05 Thread Matthias Koeppe
On Friday, March 5, 2021 at 4:08:34 PM UTC-8 Dima Pasechnik wrote:

> Matthias, 
> is it another instance of not having .pc files ready for blas/lapack etc? 
>

I don't think so. From Klaus' configure.log above, 

===
Checking whether SageMath should install SPKG openblas...
checking BLAS library... openblas
checking whether any of gfortran is installed as or will be installed as 
SPKG... no
checking for OPENBLAS... no
checking for library containing openblas_get_config... no
checking for library containing cblas_dgemm... no
checking for library containing dgeqrf... no
checking for library containing dgeqrf_... no
checking for library containing DGEQRF... no
checking for library containing DGEQRF_... no
configure: no suitable system package found for SPKG openblas
===

So Sage should have installed openblas, which always installs the correct 
.pc files. 
But who knows what may have happened in the incremental build here. 



>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/7fd455a5-6715-427c-a054-67d22aaed895n%40googlegroups.com.


Re: [sage-support] problem compiling sage 9.2 on RHEL 6

2021-03-04 Thread Matthias Koeppe
OK, time to officially remove support for building with python 2.6 as 
sage-bootstrap-python - https://trac.sagemath.org/ticket/20023 (needs 
review).

On Thursday, March 4, 2021 at 10:25:35 AM UTC-8 Dima Pasechnik wrote:

> On Thu, Mar 4, 2021 at 6:18 PM Matthias Koeppe  
> wrote:
> >
> > Looks like we cannot bootstrap using Python 2.6 any more.
> >
> > The error seen in the log is: 
> https://stackoverflow.com/questions/19668395/str-format-for-python-2-6-gives-error-where-2-7-does-not
>
> yes, but this is the secondary error, in processing ValueError thrown by
>
> https://github.com/sagemath/sage/blob/master/build/sage_bootstrap/uncompress/cmdline.py#L53
>
> >
> >
> >
> >
> > On Thursday, March 4, 2021 at 9:53:28 AM UTC-8 Dima Pasechnik wrote:
> >>
> >> On Thu, Mar 4, 2021 at 5:08 PM 'Hackenberg, Klaus' via sage-support
> >>  wrote:
> >> >
> >> > High,
> >> >
> >> >
> >> >
> >> > on my RHEL6 server I see
> >> >
> >> >
> >> >
> >> > [root@dlp762 Sage]# python --version
> >> >
> >> > Python 2.6.6
> >> >
> >> >
> >> >
> >> > But the server has installed xz packages
> >> >
> >> >
> >> >
> >> > [root@dlp762 Sage]# rpm -qa --last|grep xz
> >> >
> >> > xz-devel-4.999.9-0.5.beta.20091007git.el6.x86_64 Tue Jun 18 11:06:45 
> 2019
> >> >
> >> > xz-lzma-compat-4.999.9-0.5.beta.20091007git.el6.x86_64 Fri Sep 18 
> 09:39:37 2015
> >> >
> >> > xz-4.999.9-0.5.beta.20091007git.el6.x86_64 Fri Sep 18 09:39:26 2015
> >> >
> >> > xz-libs-4.999.9-0.5.beta.20091007git.el6.x86_64 Fri Sep 18 09:39:03 
> 2015
> >> >
> >> >
> >> >
> >> > Is it possible to use the buildin xz ?
> >>
> >> Do you have xz application installed and accepted by Sage (it should
> >> be visible in
> >> config.log)? If so, something is breaking in
> >> 
> https://github.com/sagemath/sage/blob/master/build/sage_bootstrap/uncompress/tar_file.py#L161
> >>
> >> Mind you, python 2.6.6 has been released about 12 years ago, not sure
> >> this code, from 2016, was ever tested
> >> on 2.6.6 (perhaps on less buggy 2.6.7...)
> >>
> >> You may try installing pyenv with newer python and
> >> run Sage installation from there. See 
> https://gist.github.com/ysaotome/7956676
> >> (you ought to replace 2.7.6 with 3.9.1 there, to escape the Python2
> >> hell completely)
> >>
> >>
> >> >
> >> >
> >> >
> >> > Regards, Klaus Hackenberg
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Klaus Hackenberg
> >> >
> >> > IT-Systeme und Software-Integration
> >> >
> >> > IT.SERVICES
> >> >
> >> > Ruhr-Universität Bochum | 44780 Bochum
> >> >
> >> > fon: +49 234 32 23485 <+49%20234%203223485>
> >> >
> >> > http://www.it-services.rub.de/
> >> >
> >> >
> >> >
> >> > Von: sage-s...@googlegroups.com  Im 
> Auftrag von Dima Pasechnik
> >> > Gesendet: Donnerstag, 4. März 2021 17:18
> >> > An: sage-support 
> >> > Betreff: Re: [sage-support] problem compiling sage 9.2 on RHEL 6
> >> >
> >> >
> >> >
> >> > your system python cannot uncompress .xz files... :(
> >> >
> >> >
> >> >
> >> > how old is it?
> >> >
> >> >
> >> >
> >> > can you install systemwide python2 to be python 2.7?
> >> >
> >> >
> >> >
> >> > On Thu, 4 Mar 2021, 16:04 'Hackenberg, Klaus' via sage-support, <
> sage-s...@googlegroups.com> wrote:
> >> >
> >> > High,
> >> >
> >> > I startet in a fresh directory sage-9.2 (from sage-9.2.tag.gz)
> >> > using the command " make mpir-clean" and got
> >> >
> >> > 
> =
> >> > [lsf@dlp762 sage-9.2]$ make mpir-clean
> >> > make build/make/Makefile --stop
> >> > make[1]: Entering directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2'
> >> > rm -f config.log
> >> > mkdir -p logs/pkgs
> >>

Re: [sage-support] problem compiling sage 9.2 on RHEL 6

2021-03-04 Thread Matthias Koeppe
Looks like we cannot bootstrap using Python 2.6 any more.

The error seen in the log 
is: 
https://stackoverflow.com/questions/19668395/str-format-for-python-2-6-gives-error-where-2-7-does-not




On Thursday, March 4, 2021 at 9:53:28 AM UTC-8 Dima Pasechnik wrote:

> On Thu, Mar 4, 2021 at 5:08 PM 'Hackenberg, Klaus' via sage-support
>  wrote:
> >
> > High,
> >
> >
> >
> > on my RHEL6 server I see
> >
> >
> >
> > [root@dlp762 Sage]# python --version
> >
> > Python 2.6.6
> >
> >
> >
> > But the server has installed xz packages
> >
> >
> >
> > [root@dlp762 Sage]# rpm -qa --last|grep xz
> >
> > xz-devel-4.999.9-0.5.beta.20091007git.el6.x86_64 Tue Jun 18 11:06:45 2019
> >
> > xz-lzma-compat-4.999.9-0.5.beta.20091007git.el6.x86_64 Fri Sep 18 
> 09:39:37 2015
> >
> > xz-4.999.9-0.5.beta.20091007git.el6.x86_64 Fri Sep 18 09:39:26 2015
> >
> > xz-libs-4.999.9-0.5.beta.20091007git.el6.x86_64 Fri Sep 18 09:39:03 2015
> >
> >
> >
> > Is it possible to use the buildin xz ?
>
> Do you have xz application installed and accepted by Sage (it should
> be visible in
> config.log)? If so, something is breaking in
>
> https://github.com/sagemath/sage/blob/master/build/sage_bootstrap/uncompress/tar_file.py#L161
>
> Mind you, python 2.6.6 has been released about 12 years ago, not sure
> this code, from 2016, was ever tested
> on 2.6.6 (perhaps on less buggy 2.6.7...)
>
> You may try installing pyenv with newer python and
> run Sage installation from there. See 
> https://gist.github.com/ysaotome/7956676
> (you ought to replace 2.7.6 with 3.9.1 there, to escape the Python2
> hell completely)
>
>
> >
> >
> >
> > Regards, Klaus Hackenberg
> >
> >
> >
> > --
> >
> > Klaus Hackenberg
> >
> > IT-Systeme und Software-Integration
> >
> > IT.SERVICES
> >
> > Ruhr-Universität Bochum | 44780 Bochum
> >
> > fon: +49 234 32 23485 <+49%20234%203223485>
> >
> > http://www.it-services.rub.de/
> >
> >
> >
> > Von: sage-s...@googlegroups.com  Im Auftrag 
> von Dima Pasechnik
> > Gesendet: Donnerstag, 4. März 2021 17:18
> > An: sage-support 
> > Betreff: Re: [sage-support] problem compiling sage 9.2 on RHEL 6
> >
> >
> >
> > your system python cannot uncompress .xz files... :(
> >
> >
> >
> > how old is it?
> >
> >
> >
> > can you install systemwide python2 to be python 2.7?
> >
> >
> >
> > On Thu, 4 Mar 2021, 16:04 'Hackenberg, Klaus' via sage-support, <
> sage-s...@googlegroups.com> wrote:
> >
> > High,
> >
> > I startet in a fresh directory sage-9.2 (from sage-9.2.tag.gz)
> > using the command " make mpir-clean" and got
> >
> > =
> > [lsf@dlp762 sage-9.2]$ make mpir-clean
> > make build/make/Makefile --stop
> > make[1]: Entering directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2'
> > rm -f config.log
> > mkdir -p logs/pkgs
> > ln -s logs/pkgs/config.log config.log
> > 
> 
> > error: Sage source tree is unconfigured. Please run "./configure" first.
> > note: Type "./configure --help" to see the available configuration 
> options.
> > 
> 
> > make[1]: *** [build/make/Makefile] Error 1
> > make[1]: Leaving directory 
> `/net/dlp762/share/application-software/Sage/sage-9.2'
> > make: *** [mpir-clean] Error 2
> > [lsf@dlp762 sage-9.2]$
> > =
> >
> > I then used
> >
> > ./configure --with-mp=gmp
> > make mpir-clean
> > make -j4
> >
> > and ppl-1.2 compiled !
> >
> > But now I get a new error with symmetrica-3.0.1.
> > I attach the error log file
> >
> > Regards, Klaus Hackenberg
> >
> > --
> > Klaus Hackenberg
> > IT-Systeme und Software-Integration
> > IT.SERVICES
> > Ruhr-Universität Bochum | 44780 Bochum
> > fon: +49 234 32 23485 <+49%20234%203223485>
> > http://www.it-services.rub.de/
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: sage-s...@googlegroups.com  Im Auftrag 
> von Dima Pasechnik
> > Gesendet: Donnerstag, 4. März 2021 15:57
> > An: sage-support 
> > Betreff: Re: [sage-support] problem compiling sage 9.2 on RHEL 6
> >
> > Please post the top-level config.log, then we'll see more details about 
> GMP.
> >
> > In Sage 9.2, if you do ./configure without arguments, Sage is building a 
> GMP-compatible MPIR, not "real" GMP.
> > (Perhaps MPIR is broken now beyond repair, and shoud not be used on RHEL 
> 6,I don't know) We're changing with in the coming 9.3, see
> > https://trac.sagemath.org/ticket/30752
> > Meanwhile please do
> >
> > make mpir-clean
> > ./configure --with-mp=gmp
> > make -j4
> >
> >
> > On Thu, Mar 4, 2021 at 2:06 PM 'Hackenberg, Klaus' via sage-support <
> sage-s...@googlegroups.com> wrote:
> > >
> > > High,
> > >
> > > I startet in a fresh directory sage-9.2 (from sage-9.2.tag.gz)
> > > using the commands
> > >
> > > ./configure
> > > make -j4
> > >
> > > and ran into the same error.
> > >
> > > gmp 

Re: [sage-support] Import error for lrcalc library

2021-02-01 Thread Matthias Koeppe
As Dima said, please report bugs of distribution packaging of Sage to the 
distribution.

On Monday, February 1, 2021 at 8:29:17 AM UTC-8 tiger...@gmail.com wrote:

> I should also add this.
> If from an ipython module I invoke `from sage.misc.misc_c import prod`, 
> everything works fine.
> On the other hand, `from sage.rings.all import RealField` works well 
> inside ipython, but produce a different error from a source file.
> Relevant link https://pastebin.com/AMfd0hhh
> On Monday, 1 February 2021 at 14:50:47 UTC+1 dim...@gmail.com wrote:
>
>> This has to be reported to Arch people. 
>>
>> On Mon, Feb 1, 2021 at 1:39 PM Simone Perriello  
>> wrote: 
>> > 
>> > 
>> > Operating system: ArchLinux. 
>> > Sage installed through official packages. 
>> > If I just launch `sage` from terminal it gives this stacktrace 
>> https://pastebin.com/s1FnMhe2 
>> > 
>> > The same happens if I try to do a `from sage.all import *` from 
>> ipython, from a python file or from sage -python. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups "sage-support" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to sage-support...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-support/09226af6-af8a-4353-bfbc-87bab86c3603n%40googlegroups.com.
>>  
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/6f8fcaef-3ec1-4a03-b50d-6b10ac92c945n%40googlegroups.com.


[sage-support] Re: Error building fpylll from Sage 9.2 source

2021-01-22 Thread Matthias Koeppe
This failure on Cygwin has been fixed 
in https://trac.sagemath.org/ticket/31146

On Thursday, January 21, 2021 at 10:29:41 AM UTC-8 user...@gmail.com wrote:

> While building Sage 9.2 from source, the `make` process throws an error 
> while building the "fpylll.config" extension. I believe the most relevant 
> log information is: 
>build/src/fpylll/config.cpp:1807:37: error: 'FPLLL_WITH_RECURSIVE_ENUM' 
> was not declared in this scope
>1807 |   __pyx_t_4 = __Pyx_PyBool_FromLong(FPLLL_WITH_RECURSIVE_ENUM); 
> if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 40, __pyx_L1_error)
> | ^
>   error: command 'gcc' failed with exit status 1
>
> What might cause this, and how would I fix it?
>
> (~/sage/config.log is not attached because it was a 0 byte file that can't 
> be opened, and thus couldn't be attached)
>
> If you have any questions or suggestions, please let me know.
>
>
>
> 
>  Virus-free. 
> www.avast.com 
> 
>  
> <#m_5648881936583264655_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/98e59007-6f23-48e0-8c3e-8b70f118d909n%40googlegroups.com.


Re: [sage-support] Re: Install of sage on macOS

2020-12-23 Thread Matthias Koeppe
On Wednesday, December 23, 2020 at 5:55:38 AM UTC-8 u...@ll.mit.edu wrote:

>
>>> the MacPorts-specific part would be to create a list of packages to 
>> install, and put it into build/pkgs/*/distros/macports 
>> and a similar global location.
>>
>
> I'm not sure I understand what that means.
>

You can learn about it by 
reading 
https://doc.sagemath.org/html/en/developer/packaging.html#allowing-for-the-use-of-system-packages

If you want to help with supporting MacPorts 
packages, https://trac.sagemath.org/ticket/30504 


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/db30bb01-e714-4b5f-a2cd-2fae1cf45946n%40googlegroups.com.


Re: [sage-support] Re: Building of sage 9.2 stopped with sagelib compilation - taking now system packages of Opensuse

2020-11-30 Thread Matthias Koeppe
On Monday, November 30, 2020 at 7:47:27 AM UTC-8 Dima Pasechnik wrote:

> we should get opensuse tumbleweed properly supported, with CI.
>
> this entails listing the needed packages in build/pkgs/*/distros/
> like we do for Ubuntu, Fedora, etc.
>
>>
>>
Packages for opensuse are already up in 
https://trac.sagemath.org/ticket/30619

The follow-up ticket https://trac.sagemath.org/ticket/29527 tracks the task 
of adding it to GH Actions.

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/504a0558-b448-4a61-84d6-863a256bca78n%40googlegroups.com.


[sage-support] Re: Building of sage 9.2 stopped with sagelib compilation - taking now system packages of Opensuse

2020-11-28 Thread Matthias Koeppe
The actual error is likely further up. This problem could just be the 
missing dependency of sagelib on giac, already fixed 
in https://trac.sagemath.org/ticket/30858
Try compiling the latest development version,
or do "make giac && make" to work around the problem

On Saturday, November 28, 2020 at 9:32:26 AM UTC-8 tobwe...@web.de wrote:

> Because the last g++ command is something with stl vector: Do I need the 
> glibc-static-devel? I only have glibc-devel installed.
>
> Tobias
>
>
> Tobias Weiss schrieb am Samstag, 28. November 2020 um 16:25:24 UTC+1:
>
>> Hello Everybody,
>>
>> now the second post to the problem. I try to make sage 9.2 on Opensuse 
>> Tumbleweed. The compilation stopped with last step of sagelib. If I don't 
>> take system packages, the error don't occurs.
>> (see thread https://groups.google.com/g/sage-support/c/AJRosgRDrsE)
>>
>> Pari was take from tarball this times. The output of make ends with:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *[sagelib-9.2] [296/297] creating 
>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests [sagelib-9.2] gcc 
>> -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -D_FORTIFY_SOURCE=2 
>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>> -fstack-clash-protection -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv 
>> -fno-semantic-interposition -O2 -Wall -D_FORTIFY_SOURCE=2 
>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>> -fstack-clash-protection -Werror=return-type -g -O2 -Wall 
>> -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
>> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
>> -g -fPIC -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src 
>> -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src/sage/ext 
>> -I/usr/include/python3.8 
>> -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/numpy/core/include
>>  
>> -Ibuild/cythonized -I/home/tobias/bin/sage-9.2/local/include 
>> -I/usr/include/python3.8 -c build/cythonized/sage/tests/cython.c -o 
>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/cython.o 
>> -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c99 [sagelib-9.2] 
>> gcc -pthread -shared -Wl,-rpath-link,/home/tobias/bin/sage-9.2/local/lib 
>> -L/home/tobias/bin/sage-9.2/local/lib 
>> -Wl,-rpath,/home/tobias/bin/sage-9.2/local/lib 
>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/cython.o 
>> -L/usr/lib64 -o 
>> build/lib.linux-x86_64-3.8/sage/tests/cython.cpython-38-x86_64-linux-gnu.so 
>>  [sagelib-9.2] [297/297] gcc 
>> -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -D_FORTIFY_SOURCE=2 
>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>> -fstack-clash-protection -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv 
>> -fno-semantic-interposition -O2 -Wall -D_FORTIFY_SOURCE=2 
>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>> -fstack-clash-protection -Werror=return-type -g -O2 -Wall 
>> -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
>> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
>> -g -fPIC 
>> -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/cysignals 
>> -I./sage/cpython -Isage/cpython 
>> -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src 
>> -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src/sage/ext 
>> -I/usr/include/python3.8 
>> -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/numpy/core/include
>>  
>> -Ibuild/cythonized -I/home/tobias/bin/sage-9.2/local/include 
>> -I/usr/include/python3.8 -c build/cythonized/sage/tests/stl_vector.cpp -o 
>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/stl_vector.o 
>> -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c++11 [sagelib-9.2] 
>> build/cythonized/sage/tests/stl_vector.cpp: In function ‘PyObject* 
>> __pyx_pf_4sage_5tests_10stl_vector_14stl_int_vector_4__getitem__(__pyx_obj_4sage_5tests_10stl_vector_stl_int_vector*,
>>  
>> int)’: [sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:2940:30: 
>> warning: comparison of integer expressions of different signedness: ‘int’ 
>> and ‘std::vector::size_type’ {aka ‘long unsigned int’} 
>> [-Wsign-compare] [sagelib-9.2]  2940 |   __pyx_t_1 = (__pyx_v_i < 
>> __pyx_v_self->data->size()); [sagelib-9.2]   | 
>>~~^~~~ [sagelib-9.2] 
>> build/cythonized/sage/tests/stl_vector.cpp: At global scope: [sagelib-9.2] 
>> build/cythonized/sage/tests/stl_vector.cpp:5744:18: warning: ‘PyObject* 

Re: [sage-support] Re: Building of sage 9.2 stopped with sagelib compilation - taking now system packages of Opensuse

2020-11-28 Thread Matthias Koeppe
Those who want to help with this problem may 
find https://trac.sagemath.org/ticket/30619 useful -- builds on this system 
can be reproduced using "tox -e docker-opensuse-tumbleweed-standard"


On Saturday, November 28, 2020 at 10:23:52 AM UTC-8 Dima Pasechnik wrote:

> please post the top-level config.log
>
>
>
> On Sat, 28 Nov 2020, 17:32 Tobias Weiss,  wrote:
>
>> Because the last g++ command is something with stl vector: Do I need the 
>> glibc-static-devel? I only have glibc-devel installed.
>>
>> Tobias
>>
>>
>> Tobias Weiss schrieb am Samstag, 28. November 2020 um 16:25:24 UTC+1:
>>
>>> Hello Everybody,
>>>
>>> now the second post to the problem. I try to make sage 9.2 on Opensuse 
>>> Tumbleweed. The compilation stopped with last step of sagelib. If I don't 
>>> take system packages, the error don't occurs.
>>> (see thread https://groups.google.com/g/sage-support/c/AJRosgRDrsE)
>>>
>>> Pari was take from tarball this times. The output of make ends with:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *[sagelib-9.2] [296/297] creating 
>>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests [sagelib-9.2] gcc 
>>> -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -D_FORTIFY_SOURCE=2 
>>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>>> -fstack-clash-protection -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv 
>>> -fno-semantic-interposition -O2 -Wall -D_FORTIFY_SOURCE=2 
>>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>>> -fstack-clash-protection -Werror=return-type -g -O2 -Wall 
>>> -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
>>> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
>>> -g -fPIC -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src 
>>> -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src/sage/ext 
>>> -I/usr/include/python3.8 
>>> -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/numpy/core/include
>>>  
>>> -Ibuild/cythonized -I/home/tobias/bin/sage-9.2/local/include 
>>> -I/usr/include/python3.8 -c build/cythonized/sage/tests/cython.c -o 
>>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/cython.o 
>>> -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c99 [sagelib-9.2] 
>>> gcc -pthread -shared -Wl,-rpath-link,/home/tobias/bin/sage-9.2/local/lib 
>>> -L/home/tobias/bin/sage-9.2/local/lib 
>>> -Wl,-rpath,/home/tobias/bin/sage-9.2/local/lib 
>>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/cython.o 
>>> -L/usr/lib64 -o 
>>> build/lib.linux-x86_64-3.8/sage/tests/cython.cpython-38-x86_64-linux-gnu.so 
>>>  [sagelib-9.2] [297/297] gcc 
>>> -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -D_FORTIFY_SOURCE=2 
>>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>>> -fstack-clash-protection -Werror=return-type -g -DOPENSSL_LOAD_CONF -fwrapv 
>>> -fno-semantic-interposition -O2 -Wall -D_FORTIFY_SOURCE=2 
>>> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables 
>>> -fstack-clash-protection -Werror=return-type -g -O2 -Wall 
>>> -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
>>> -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type 
>>> -g -fPIC 
>>> -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/cysignals 
>>> -I./sage/cpython -Isage/cpython 
>>> -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src 
>>> -I/home/tobias/bin/sage-9.2/build/pkgs/sagelib/src/sage/ext 
>>> -I/usr/include/python3.8 
>>> -I/home/tobias/bin/sage-9.2/local/lib64/python3.8/site-packages/numpy/core/include
>>>  
>>> -Ibuild/cythonized -I/home/tobias/bin/sage-9.2/local/include 
>>> -I/usr/include/python3.8 -c build/cythonized/sage/tests/stl_vector.cpp -o 
>>> build/temp.linux-x86_64-3.8/build/cythonized/sage/tests/stl_vector.o 
>>> -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c++11 [sagelib-9.2] 
>>> build/cythonized/sage/tests/stl_vector.cpp: In function ‘PyObject* 
>>> __pyx_pf_4sage_5tests_10stl_vector_14stl_int_vector_4__getitem__(__pyx_obj_4sage_5tests_10stl_vector_stl_int_vector*,
>>>  
>>> int)’: [sagelib-9.2] build/cythonized/sage/tests/stl_vector.cpp:2940:30: 
>>> warning: comparison of integer expressions of different signedness: ‘int’ 
>>> and ‘std::vector::size_type’ {aka ‘long unsigned int’} 
>>> [-Wsign-compare] [sagelib-9.2]  2940 |   __pyx_t_1 = (__pyx_v_i < 
>>> __pyx_v_self->data->size()); [sagelib-9.2]   

[sage-support] Re: Problem with load in sagemath 9.0 on ubuntu 20.04

2020-10-20 Thread Matthias Koeppe
On Tuesday, October 20, 2020 at 11:57:21 AM UTC-7, Carl Eberhart wrote:
>
> Thanks.   After looking for the definition of of preparse_file it appears 
> that it is imported from a binary file.  Will I have to download the source 
> and recompile to fix this?
>

Your code  in orthogtraps19.sage likely contains <> and needs updating.


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/54b75ed5-be5d-427b-a6bf-56bfdef2f542o%40googlegroups.com.


[sage-support] Re: Problem with load in sagemath 9.0 on ubuntu 20.04

2020-10-19 Thread Matthias Koeppe
On Monday, October 19, 2020 at 10:36:05 AM UTC-7, Carl Eberhart wrote:
>
> I can't load a sage file in either the notebook or terminal version of Sage
>   File "", line 121
> if s<>_sage_const_0 :
>  ^
> SyntaxError: invalid syntax
>

The syntax <> for "not equal"  is no longer valid in Python 3. Use != 
instead.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/da812ca0-a143-4c8e-b2ee-62056a3e61a7o%40googlegroups.com.


Re: [sage-support] compile problem for sage 9.2.b9 on mac 11.0 big sur

2020-09-02 Thread Matthias Koeppe
I also see build failures of at least some of these packages at 
https://github.com/mkoeppe/sage/runs/1059961873 (using a new GH workflow 
that runs Xcode 12 beta, added in https://trac.sagemath.org/ticket/30487)

I have opened https://trac.sagemath.org/ticket/30494 "Meta-ticket: Support 
Xcode 12, macOS 11 Big Sur"

On Wednesday, September 2, 2020 at 8:19:37 AM UTC-7, John H Palmieri wrote:
>
> With a system Python and "make -k", the following packages fail:
>
> gf2x
> ecm
> symmetrica
> rubiks
> ecl
> scipy
>
> On Tuesday, September 1, 2020 at 10:29:52 PM UTC-7 Matthias Koeppe wrote:
>
>> These lines:
>>
>> configure:17396: checking build system compiler gcc
>>
>> etc.
>> might indicate that the configure script is confused about cross 
>> compiling to a different architecture.
>>
>>
>> On Tuesday, September 1, 2020 at 9:59:59 PM UTC-7, John H Palmieri wrote:
>>>
>>>
>>>
>>> On Tuesday, September 1, 2020 at 9:52:37 PM UTC-7 Matthias Koeppe wrote:
>>>
>>>> On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri 
>>>> wrote:
>>>>
>>>>> If I do install Python 3.7, then gf2x and ecm both fail to build. The 
>>>>> gf2x log file says "configure: error: Cannot find a build system compiler
>>>>> ". The ecm log file says "checking if globals are prefixed by 
>>>>> underscore... configure: error: Test program links neither with nor 
>>>>> without 
>>>>> underscore."
>>>>>
>>>>>>
>>>>>>>
>>>> gf2x was just upgraded in https://trac.sagemath.org/ticket/30412 - 
>>>> merged in 9.2.beta11. Did you test with this beta or an earlier one?
>>>>
>>>
>>> I tried with 9.2.beta10, and just now I tried with this new version of 
>>> gf2x. Same error either way. Here is the gf2x config.log. 
>>>
>>>>
>>>>  
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/977efba9-1756-4c28-b23d-d7698b9c02a7o%40googlegroups.com.


Re: [sage-support] compile problem for sage 9.2.b9 on mac 11.0 big sur

2020-09-01 Thread Matthias Koeppe
These lines:

configure:17396: checking build system compiler gcc

etc.
might indicate that the configure script is confused about cross compiling 
to a different architecture.


On Tuesday, September 1, 2020 at 9:59:59 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, September 1, 2020 at 9:52:37 PM UTC-7 Matthias Koeppe wrote:
>
>> On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>>
>>> If I do install Python 3.7, then gf2x and ecm both fail to build. The 
>>> gf2x log file says "configure: error: Cannot find a build system compiler
>>> ". The ecm log file says "checking if globals are prefixed by 
>>> underscore... configure: error: Test program links neither with nor without 
>>> underscore."
>>>
>>>>
>>>>>
>> gf2x was just upgraded in https://trac.sagemath.org/ticket/30412 - 
>> merged in 9.2.beta11. Did you test with this beta or an earlier one?
>>
>
> I tried with 9.2.beta10, and just now I tried with this new version of 
> gf2x. Same error either way. Here is the gf2x config.log. 
>
>>
>>  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/882e8bef-1e45-4ade-83d0-a7b22a03f4f2o%40googlegroups.com.


Re: [sage-support] compile problem for sage 9.2.b9 on mac 11.0 big sur

2020-09-01 Thread Matthias Koeppe
On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>
> If I do install Python 3.7, then gf2x and ecm both fail to build. The gf2x 
> log file says "configure: error: Cannot find a build system compiler
> ". The ecm log file says "checking if globals are prefixed by 
> underscore... configure: error: Test program links neither with nor without 
> underscore."
>
>>
>>>
gf2x was just upgraded in https://trac.sagemath.org/ticket/30412 - merged 
in 9.2.beta11. Did you test with this beta or an earlier one?

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/80dee51d-41eb-4b55-a479-f2fc477ac89do%40googlegroups.com.


Re: [sage-support] compile problem for sage 9.2.b9 on mac 11.0 big sur

2020-09-01 Thread Matthias Koeppe
This fix was already merged in 3.8.4, so 
after https://trac.sagemath.org/ticket/27754 we should be fine.

The PR for Python 3.7 is https://github.com/python/cpython/pull/21155, but 
our Python 3.7.x is very old already.

On Tuesday, September 1, 2020 at 9:43:15 PM UTC-7, Matthias Koeppe wrote:
>
> The issue with "posixmodule" is apparently 
> https://bugs.python.org/issue41100
>
>
>
> On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>>
>> If I do install Python 3.7, then gf2x and ecm both fail to build. The 
>> gf2x log file says "configure: error: Cannot find a build system compiler
>> ". The ecm log file says "checking if globals are prefixed by 
>> underscore... configure: error: Test program links neither with nor without 
>> underscore."
>>
>> On Tuesday, September 1, 2020 at 8:38:47 PM UTC-7 John H Palmieri wrote:
>>
>>> I've been trying to build on Big Sur, too. I removed the 
>>> MACOSX_DEPLOYMENT_TARGET lines from sage-env, but the Python build still 
>>> fails. The log file is attached. Any suggestions (besides installing a 
>>> different system version of Python)?
>>>
>>>   John
>>>
>>> On Saturday, August 22, 2020 at 3:44:01 PM UTC-7 dim...@gmail.com wrote:
>>>
>>>> On Sat, Aug 22, 2020 at 11:23 PM David Joyner  
>>>> wrote: 
>>>> > 
>>>> > 
>>>> > 
>>>> > On Sat, Aug 22, 2020 at 6:02 PM Dima Pasechnik  
>>>> wrote: 
>>>> >> 
>>>> >> On Sat, Aug 22, 2020 at 10:51 PM David Joyner  
>>>> wrote: 
>>>> >> > 
>>>> >> > 
>>>> >> > 
>>>> >> > On Sat, Aug 22, 2020 at 4:52 PM Dima Pasechnik  
>>>> wrote: 
>>>> >> >> 
>>>> >> >> On Sat, Aug 22, 2020 at 8:28 PM Dima Pasechnik  
>>>> wrote: 
>>>> >> >> > 
>>>> >> >> > note: 'utimensat' has been marked as being introduced in macOS 
>>>> 10.13 
>>>> >> >> > here, but the deployment target is macOS 10.9.0 
>>>> >> >> > 
>>>> >> >> > seems to indicate that one has to properly set 
>>>> MACOS_DEPLOYMENT_TARGET 
>>>> >> >> > (or a suchlike thing) to 10.13 or even bigger. 
>>>> >> >> 
>>>> >> >> indeed, in src/bin/sage-env on has 
>>>> >> >> 
>>>> >> >> MACOSX_DEPLOYMENT_TARGET=10.9 
>>>> >> >> 
>>>> >> >> which is the reason for that error, I guess. 
>>>> >> > 
>>>> >> > 
>>>> >> > Shouldn't it be 11.0? 
>>>> >> > 
>>>> >> > I changed it then tried to recompile but it stopped at the same 
>>>> place. 
>>>> >> > I can't install a system python3 using homebrew since it's broken 
>>>> >> > https://github.com/Homebrew/brew/issues/7803 
>>>> >> 
>>>> >> you can install a binary python3.7 from python.org - this is known 
>>>> to 
>>>> >> be possible to use in Sage on macOS 10.15 and earlier versions. 
>>>> >> 
>>>> > 
>>>> > I installed both python 3.8.5 (the latest) and when that failed 
>>>> 3.7.9. 
>>>> > 
>>>> > The end of the output of configure is this seeming contradictory 
>>>> info: 
>>>> > 
>>>> > configure: notice: the following SPKGs did not find equivalent system 
>>>> packages: brial cbc cddlib cliquer coxeter3 eclib ecm fflas_ffpack flintqs 
>>>> fplll gf2x gfan givaro glpk gp2c gsl iconv iml lcalc libatomic_ops 
>>>> libbraiding libsemigroups lrcalc m4ri m4rie nauty ninja_build openblas 
>>>> palp 
>>>> pandoc pari pari_elldata pari_galdata pari_galpol pari_nftables 
>>>> pari_seadata pari_seadata_small pcre perl_cpan_polymake_prereq 
>>>> perl_term_readline_gnu planarity ppl python3 r rw suitesparse symmetrica 
>>>> sympow tachyon yasm zeromq zn_poly 
>>>>
>>>> This notice is more about ./configure being confused whether there is 
>>>> Homebrew or Conda installed. 
>>>>
>>>> The interesting line of ./configure output is above that notice: 
>>>>
>>>> python3-3.7.3.p1: using system package; 
>>

Re: [sage-support] compile problem for sage 9.2.b9 on mac 11.0 big sur

2020-09-01 Thread Matthias Koeppe
The issue with "posixmodule" is apparently 
https://bugs.python.org/issue41100



On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>
> If I do install Python 3.7, then gf2x and ecm both fail to build. The gf2x 
> log file says "configure: error: Cannot find a build system compiler
> ". The ecm log file says "checking if globals are prefixed by 
> underscore... configure: error: Test program links neither with nor without 
> underscore."
>
> On Tuesday, September 1, 2020 at 8:38:47 PM UTC-7 John H Palmieri wrote:
>
>> I've been trying to build on Big Sur, too. I removed the 
>> MACOSX_DEPLOYMENT_TARGET lines from sage-env, but the Python build still 
>> fails. The log file is attached. Any suggestions (besides installing a 
>> different system version of Python)?
>>
>>   John
>>
>> On Saturday, August 22, 2020 at 3:44:01 PM UTC-7 dim...@gmail.com wrote:
>>
>>> On Sat, Aug 22, 2020 at 11:23 PM David Joyner  
>>> wrote: 
>>> > 
>>> > 
>>> > 
>>> > On Sat, Aug 22, 2020 at 6:02 PM Dima Pasechnik  
>>> wrote: 
>>> >> 
>>> >> On Sat, Aug 22, 2020 at 10:51 PM David Joyner  
>>> wrote: 
>>> >> > 
>>> >> > 
>>> >> > 
>>> >> > On Sat, Aug 22, 2020 at 4:52 PM Dima Pasechnik  
>>> wrote: 
>>> >> >> 
>>> >> >> On Sat, Aug 22, 2020 at 8:28 PM Dima Pasechnik  
>>> wrote: 
>>> >> >> > 
>>> >> >> > note: 'utimensat' has been marked as being introduced in macOS 
>>> 10.13 
>>> >> >> > here, but the deployment target is macOS 10.9.0 
>>> >> >> > 
>>> >> >> > seems to indicate that one has to properly set 
>>> MACOS_DEPLOYMENT_TARGET 
>>> >> >> > (or a suchlike thing) to 10.13 or even bigger. 
>>> >> >> 
>>> >> >> indeed, in src/bin/sage-env on has 
>>> >> >> 
>>> >> >> MACOSX_DEPLOYMENT_TARGET=10.9 
>>> >> >> 
>>> >> >> which is the reason for that error, I guess. 
>>> >> > 
>>> >> > 
>>> >> > Shouldn't it be 11.0? 
>>> >> > 
>>> >> > I changed it then tried to recompile but it stopped at the same 
>>> place. 
>>> >> > I can't install a system python3 using homebrew since it's broken 
>>> >> > https://github.com/Homebrew/brew/issues/7803 
>>> >> 
>>> >> you can install a binary python3.7 from python.org - this is known 
>>> to 
>>> >> be possible to use in Sage on macOS 10.15 and earlier versions. 
>>> >> 
>>> > 
>>> > I installed both python 3.8.5 (the latest) and when that failed 3.7.9. 
>>> > 
>>> > The end of the output of configure is this seeming contradictory info: 
>>> > 
>>> > configure: notice: the following SPKGs did not find equivalent system 
>>> packages: brial cbc cddlib cliquer coxeter3 eclib ecm fflas_ffpack flintqs 
>>> fplll gf2x gfan givaro glpk gp2c gsl iconv iml lcalc libatomic_ops 
>>> libbraiding libsemigroups lrcalc m4ri m4rie nauty ninja_build openblas palp 
>>> pandoc pari pari_elldata pari_galdata pari_galpol pari_nftables 
>>> pari_seadata pari_seadata_small pcre perl_cpan_polymake_prereq 
>>> perl_term_readline_gnu planarity ppl python3 r rw suitesparse symmetrica 
>>> sympow tachyon yasm zeromq zn_poly 
>>>
>>> This notice is more about ./configure being confused whether there is 
>>> Homebrew or Conda installed. 
>>>
>>> The interesting line of ./configure output is above that notice: 
>>>
>>> python3-3.7.3.p1: using system package; 
>>> SPKG will not be installed 
>>>
>>> - if it's there then system Python will be used. 
>>> Otherwise, look in config.log for more details. 
>>>
>>> HTH 
>>> Dima 
>>>
>>>
>>> > 
>>> > checking for the package system in use... unknown 
>>> > 
>>> > wdj@jeeves sage-9.2.beta9 % which python3 
>>> > 
>>> > /usr/local/bin/python3 
>>> > 
>>> > wdj@jeeves sage-9.2.beta9 % python3 --version 
>>> > 
>>> > Python 3.7.9 
>>> > 
>>> > There isn't a python3 system package but there is? 
>>> > 
>>> >> 
>>> >> > 
>>> >> > 
>>> >> >> 
>>> >> >> 
>>> >> >> > 
>>> >> >> > On Sat, Aug 22, 2020 at 8:06 PM David Joyner  
>>> wrote: 
>>> >> >> > > 
>>> >> >> > > Hi: 
>>> >> >> > > 
>>> >> >> > > I don't know if this has been discussed yet but 
>>> >> >> > > I just upgraded to mac os 11.0. I downloaded 
>>> >> >> > > sage 9.2.b9 and ran make. I got a "you must 
>>> >> >> > > run ./configure first message, which I did. 
>>> >> >> > > Then I ran make and the compilation stopped while 
>>> >> >> > > compiling python 3. The log is attached. 
>>> >> >> > > 
>>> >> >> > > - David Joyner 
>>> >> >> > > 
>>> >> >> > > 
>>> >> >> > > -- 
>>> >> >> > > You received this message because you are subscribed to the 
>>> Google Groups "sage-support" group. 
>>> >> >> > > To unsubscribe from this group and stop receiving emails from 
>>> it, send an email to sage-support...@googlegroups.com. 
>>> >> >> > > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-support/CAEQuuAVjRasvOnj7NKQGfXxjL2g9XPfi8WFXdO-6A3mZ_XedHg%40mail.gmail.com.
>>>  
>>>
>>> >> >> 
>>> >> >> -- 
>>> >> >> You received this message because you are subscribed to the Google 
>>> Groups "sage-support" group. 
>>> >> >> To unsubscribe from this group and stop receiving 

[sage-support] Re: Sage Crash Report: `TypeError` upon startup (Sage 9.0.0)

2020-08-03 Thread Matthias Koeppe
Problems with the Ubuntu packaging should be reported as an Ubuntu bug.

On Sunday, August 2, 2020 at 11:31:57 PM UTC-7, Samuel Tang wrote:
>
> Hi,
>
> Thanks for your quick response. I am running on Ubuntu 20.04, and 
> installed Sagemath via `sudo apt-get install sagemath`.
> From what I recorded, it was Sage 9.0 on Python 3.8.2 since I've installed 
> Ubuntu (in early July The version are consistent on Sage and Python when I 
> referred just now:
>
> ```
> $ sage --version
> SageMath version 9.0, Release Date: 2020-01-01
>
> $ python --version
> Python 3.8.2
> ```
>
> Since I was using Sage in a daily basis in the previous week, so I think 
> I've triggered something lately causing the problem.
> Moreover I found an entry from /var/log/dpkg.log.1 that may cause the 
> problem (unsure about that).
>
> ```
> 2020-07-30 11:52:47 upgrade python3-distupgrade:all 1:20.04.21 1:20.04.23
> 2020-07-30 11:52:47 status half-configured python3-distupgrade:all 
> 1:20.04.21
> 2020-07-30 11:52:47 status unpacked python3-distupgrade:all 1:20.04.21
> 2020-07-30 11:52:47 status half-installed python3-distupgrade:all 
> 1:20.04.21
> 2020-07-30 11:52:48 status unpacked python3-distupgrade:all 1:20.04.23
> ```
>
> Should I downgrade my Python version to see if Sage could start up 
> properly? Thanks much!
> slelievre在 2020年8月3日星期一下午1:57:05 [UTC+8]寫道:
>
>> Le lundi 3 août 2020 05:31:01 UTC+2, Samuel Tang a écrit :
>>>
>>> Hi team,
>>>
>>> This issue happened to me just one day ago.
>>>
>>> I am aware of https://trac.sagemath.org/ticket/18492 and
>>>
>> https://www.mail-archive.com/debian-b...@lists.debian.org/msg1671690.html 
>>> 
>>>
>> as they have the same TypeError, but I think that is not my case.
>>>
>>> Thanks for the help in advance!
>>>
>>
>> Hi Samuel,
>>
>> Did you just install Sage? Probably not or you would have installed
>> either Sage 9.1 or Sage 9.2.beta7.
>>
>> More likely, did you have Sage installed on your computer for a while,
>> via some package manager, and working well, and did you just upgrade
>> the system Python from Python 3.7.x to Python 3.8.x?
>>
>> Python 3.8.x is not supported yet, we're slowly getting there, see:
>>
>> - Sage Trac ticket 27754
>>   Upgrade: Python 3.8.5
>>   https://trac.sagemath.org/ticket/27754
>>
>> For more support, what is your OS and how did you install Sage?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/879f29ad-61bf-428b-be67-7712af401720o%40googlegroups.com.


[sage-support] Re: Sage 9.1 dependency problem

2020-07-28 Thread Matthias Koeppe
You could deactivate conda and try again.

On Tuesday, July 28, 2020 at 8:33:38 PM UTC-7, Luis Enriquez-Contreras 
wrote:
>
> OS: Linux Mint 20 
>
> SageMath: sage-9.1-Ubuntu_18.04-x86_64.tar.bz2
>
> Hello all, I am trying to install sage 9.1, but I get this error after the 
> ./configure
> configure: notice: the following SPKGs did not find equivalent system 
> packages: boost cbc freetype gp2c isl libsemigroups pari_elldata 
> pari_galpol pari_nftables pari_seadata perl_cpan_polymake_prereq 
> perl_term_readline_gnu python3 checking for the package system in use... 
> conda configure: hint: installing the following system packages is 
> recommended and may avoid building some of the above SPKGs from source: 
> configure: $ conda install boost-cpp coincbc freetype isl pari-galpol 
> pari-seadata configure: After installation, re-run configure using: 
> configure: $ ./config.status --recheck && ./config.status 
>
> After installing those packages:
> */opt/SageMath*$ conda install -c conda-forge boost-cpp coincbc freetype 
> isl pari-galpol pari-seadata I still get the same error when I rerun 
> ./configure. I tried running make to see what would happen, and I get this: 
> *** 
> Error building Sage. The following package(s) may have failed to build (not 
> necessarily during this run of 'make all-start'): * package: 
> python3-3.7.3.p1 last build time: Jul 21 16:25 log file: 
> /opt/SageMath/logs/pkgs/python3-3.7.3.p1.log build directory: 
> /opt/SageMath/local/var/tmp/sage/build/python3-3.7.3.p1 It is safe to 
> delete any log files and build directories, but they contain information 
> that is helpful for debugging build problems. WARNING: If you now run 
> 'make' again, the build directory of the same version of the package will, 
> by default, be deleted. Set the environment variable 
> SAGE_KEEP_BUILT_SPKGS=yes to prevent this. make[1]: *** [Makefile:33: 
> all-start] Error 1 make[1]: Leaving directory '/opt/SageMath' make: *** 
> [Makefile:13: all] Error 2 
>
> I am not sure what is wrong. I installed the dependency packages first as 
> well. 
> $ sudo apt-get install bc binutils bzip2 ca-certificates cliquer curl 
> eclib-tools fflas-ffpack flintqs g++ g++ gcc gcc gfan gfortran git 
> glpk-utils gmp-ecm lcalc libatomic-ops-dev libboost-dev libbraiding-dev 
> libbz2-dev libcdd-dev libcdd-tools libcliquer-dev libcurl4-openssl-dev 
> libec-dev libecm-dev libffi-dev libflint-arb-dev libflint-dev 
> libfreetype6-dev libgd-dev libgf2x-dev libgivaro-dev libglpk-dev libgmp-dev 
> libgsl-dev libiml-dev liblfunction-dev liblrcalc-dev liblzma-dev 
> libm4rie-dev libmpc-dev libmpfi-dev libmpfr-dev libncurses5-dev libntl-dev 
> libopenblas-dev libpari-dev libpcre3-dev libplanarity-dev libppl-dev 
> libreadline-dev librw-dev libsqlite3-dev libsymmetrica2-dev libz-dev 
> libzmq3-dev m4 make nauty pari-doc pari-elldata pari-galdata pari-galpol 
> pari-gp2c pari-seadata patch perl pkg-config planarity ppl-dev python3 
> python3-distutils python3.7 r-base-dev r-cran-lattice sqlite3 tachyon tar 
> xz-utils yasm I could not get libpython3.7-dev to install; the package 
> does not seem available, but i could get the python 3.8 version. 
>
> Thank you for all the help
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/f4879cd7-54a5-4439-9234-ea801063e9d2o%40googlegroups.com.


[sage-support] Re: Pillow compilation fails to find zlib headers

2020-07-10 Thread Matthias Koeppe
This is now https://trac.sagemath.org/ticket/30103

On Friday, July 10, 2020 at 7:42:45 AM UTC-7, Maxime Boissonneault wrote:
>
> Hi,
> I am compiling Sage from source on Linux, on a supercomputer. Libraries 
> and headers are in non-standard locations. When the make tries to build 
> pillow, it fails with the following relevant part of the log. Note that it 
> initially finds zlib.h just fine. However, it seems to fail to tell pillow 
> where to take zlib from.
>
> $ grep zlib 
> /tmp/eb-6u0oyvfw/easybuild-SageMath-9.1-20200709.205356.xAMAc.log
> checking bzlib.h usability... yes
> checking bzlib.h presence... yes
> checking for bzlib.h... yes
> Checking whether SageMath should install SPKG zlib...
> checking zlib.h usability... yes
> checking zlib.h presence... yes
> checking for zlib.h... yes
> configure: will use system package and not install SPKG zlib
> checking whether any of atlas openblas zlib bzip2 is installed as or will 
> be installed as SPKG... yes; install cbc as well
> checking installing zlib? ... no
> checking whether any of gmp mpir zlib is installed as or will be installed 
> as SPKG... no
> checking for python3 >= 3.7.3, < 3.8 with modules sqlite3, ctypes, math, 
> hashlib, crypt, readline, socket, zlib, distutils.core...
> checking for python3 >= 3.7.3, < 3.8 with modules sqlite3, ctypes, math, 
> hashlib, crypt, readline, socket, zlib, distutils.core... /cvmfs/
> soft.computecanada.ca/gentoo/2020/usr/bin/python3.7
> zlib-1.2.11.p0:  using system package; SPKG 
> will not be installed
> [gap-4.10.2.p1] checking zlib.h usability... yes
> [gap-4.10.2.p1] checking zlib.h presence... yes
> [gap-4.10.2.p1] checking for zlib.h... yes
> [pillow-5.3.0.p0] Looking for `zlib` using pkg-config.
> [pillow-5.3.0.p0] Looking for zlib
> [pillow-5.3.0.p0] Checking for include file zlib.h in /cvmfs/
> soft.computecanada.ca/easybuild/software/2020/avx2/Core/sagemath/9.1/sage-9.1/local/var/tmp/sage/build/pillow-5.3.0.p0/src/src/libImaging
> [pillow-5.3.0.p0] Checking for include file zlib.h in /cvmfs/
> soft.computecanada.ca/gentoo/2020/usr/include/openjpeg-2.3
> [pillow-5.3.0.p0] Checking for include file zlib.h in /cvmfs/
> soft.computecanada.ca/gentoo/2020/usr/include/freetype2
> [pillow-5.3.0.p0] Checking for include file zlib.h in /cvmfs/
> soft.computecanada.ca/easybuild/software/2020/avx2/Core/sagemath/9.1/sage-9.1/local/include
> [pillow-5.3.0.p0] Checking for include file zlib.h in /usr/local/include
> [pillow-5.3.0.p0] Checking for include file zlib.h in /usr/include
> [pillow-5.3.0.p0] Checking for include file zlib.h in /cvmfs/
> soft.computecanada.ca/easybuild/software/2020/avx2/Core/sagemath/9.1/sage-9.1/local/include
> [pillow-5.3.0.p0] Checking for include file zlib.h in /cvmfs/
> soft.computecanada.ca/gentoo/2020/usr/include/python3.7m
> [pillow-5.3.0.p0] The headers or library files could not be found for zlib,
> [pillow-5.3.0.p0] __main__.RequiredDependencyException: zlib
> [pillow-5.3.0.p0] The headers or library files could not be found for zlib,
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/d16d14fb-e716-42cf-938e-6a177fa2cadao%40googlegroups.com.


Re: [sage-support] Re: Sage 9.1 build fails on cygwin due to lack of xlocale.h in the new cygwin-devel package

2020-05-29 Thread Matthias Koeppe


On Thursday, May 28, 2020 at 2:13:30 PM UTC-7, Dima Pasechnik wrote:
>
> On Thu, May 28, 2020 at 7:10 PM Matthias Koeppe 
> > wrote: 
> > 
> > On Thursday, May 28, 2020 at 7:21:35 AM UTC-7, ilyub wrote: 
> >> 
> >> The cygwin people seemed to have removed the physical file (xlocale.h) 
> from the cygwin distribution starting with version 3.1.1-1   
> https://cygwin.com/packages/summary/cygwin-devel.html. 
> >> Because the include file is missing, sage build fails because the numpy 
> module has an include of xlocale.h . 
> >>>> 
> >>>> 
> > 
> > Is upstream numpy aware of this issue? 
>
> It has been done and dusted in numpy: 
> https://github.com/numpy/numpy/pull/8367 
>
> they took Sage's patch from embray, and then Sage's patch was removed. 
> I have no idea why this pops up again. 
> Please post the logs. 
>
>
Indeed we need to see the logs to know what is happening on the reporter's 
machine.

Numpy within Sage 9.1 builds just fine on current Cygwin (with 3.1.4) -- 
see https://github.com/sagemath/sage/runs/694846429?check_suite_focus=true


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/3ebd8c75-7add-41e5-91f9-efa83d24294b%40googlegroups.com.


Re: [sage-support] Re: Sage 9.1 build fails on cygwin due to lack of xlocale.h in the new cygwin-devel package

2020-05-28 Thread Matthias Koeppe
On Thursday, May 28, 2020 at 7:21:35 AM UTC-7, ilyub wrote:
>
> The cygwin people seemed to have removed the physical file (xlocale.h) 
> from the cygwin distribution starting with version 3.1.1-1   
> https://cygwin.com/packages/summary/cygwin-devel.html.
> Because the include file is missing, sage build fails because the numpy 
> module has an include of xlocale.h .
>
>>
>>>
Is upstream numpy aware of this issue?
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c3fdd81b-e6a4-4f1f-94e9-088a6d803491%40googlegroups.com.


Re: [sage-support] How do you use SageMath in research, education, ...?

2020-05-26 Thread Matthias Koeppe
On Saturday, May 23, 2020 at 9:23:38 AM UTC-7, pedrito...@gmail.com wrote:
>
> Matthias,
> In teaching,
>
> https://cursos-0-fc-ugr.github.io/Matematicas/derivadas-app-estudio-func-thebelab.html
>
> https://github.com/pedritomelenas/Algebra-conmutativa-y-computacional
>
>
> https://github.com/pedritomelenas/Algebra-II/blob/master/Grafos/Grafos%20con%20sage.ipynb
>
> All in Spanish, sorry...
>
>>
>>
Looking great! 

People interested in Sage for education -- we have scheduled a Sage in 
Education Discussion. See schedule at 
https://researchseminars.org/talk/SageDays109/19/

If you would like to contribute short presentations, please let the host 
know during the discussion.


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/cd1d23b1-4060-4710-99c2-22af05a9583c%40googlegroups.com.


Re: [sage-support] Re: How do you use SageMath in research, education, ...?

2020-05-26 Thread Matthias Koeppe
On Tuesday, May 26, 2020 at 2:09:20 PM UTC-7, David Joyner wrote:
>
>
>
> On Tue, May 26, 2020 at 4:58 PM Matthias Koeppe  > wrote: 
>
>>
>> There is now a schedule at  
>> https://researchseminars.org/seminar/SageDays109
>>
>
> Are the times listed PST?
>

They are listed in your local timezone or the timezone that you configured. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/48af30d8-0dff-4fe4-9364-4ee10710be93%40googlegroups.com.


[sage-support] Re: How do you use SageMath in research, education, ...?

2020-05-26 Thread Matthias Koeppe
On Saturday, May 23, 2020 at 11:25:56 PM UTC-7, Matthias Koeppe wrote:
>
> On Saturday, May 23, 2020 at 12:18:08 PM UTC-7, Ingo Dahn wrote:
>>
>> Sounds like an interesting event, what is the intended audience? 
>> Developers? Researchers? Educators?
>>
>
> All of the above. We have added some more information at 
> https://wiki.sagemath.org/days109
>  
>
>> Specific times/tracks for each? 
>>
>
> Yes, we will announce a detailed program shortly.
>  
>

There is now a schedule at  https://researchseminars.org/seminar/SageDays109

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/ee65513f-55a2-417e-ad32-cde332c5015c%40googlegroups.com.


[sage-support] Schedule for Global Virtual SageDays 109 - May 27-29

2020-05-26 Thread Matthias Koeppe
Scheduled presentations:

   - Fredrik Strömberg - An introduction to SageMath and Python
   - Jean-Philippe Labbé - Combinatorics and geometry of polyhedra in Sage
   - Krystal Guo - Using SageMath in Algebraic Graph Theory
   - Alex J. Best - Computations with p-adic polylogarithms in Sage
   - Edinah Gnang - Broadening the Linear Algebra Toolkit to a theory of 
   constructs
   - Karl-Dieter Crisman - PreTeXt: Write Once, Read Anywhere - with Sage
   - Karl-Dieter Crisman - PreTeXt - nuts and bolts
   - William Hart - Introduction to Flint
   - William Hart - Flint-2.6.0 -- the biggest update in 5 years!
   - Julian Rüth - Introduction to running SageMath in Docker
   - Matthias Köppe - Tutorial for developers: Portability testing of the Sage 
   distribution using Docker and the Sage distro-package database
   - Haroldo G. Santos - On the design of Python-MIP: Why another Python 
optimization 
   library?
   - Travis Scrimshaw - Constructing algebraic objects with the category 
framework 
   in Sage
   - Karl-Dieter Crisman (host): Open discussion: Sage in Education
   - John Palmieri, Nicolas M. Thiéry, and others - Panel discussion: Future 
   development directions for SageMath
   - Túlio Toffolo - An Introduction to Python-MIP: Building an Effective 
Traveling 
   Salesman Problem Solver in 30 Minutes with Python-MIP
   - Kiran Kedlaya - Torsion closures of ideals
   - Jonathan Kliem - Combinatorics and recent and ongoing development of 
Polyhedra 
   in Sage
   - Anne Schilling - Markov chains through semigroup graph expansions
   - Kwankyu Lee - New in Sage 9.1: Integral curves over finite fields with 
function 
   fields

Details, schedule, free registration: https://wiki.sagemath.org/days109

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/f8a960f3-89db-43ee-9eea-ee55e2f39595%40googlegroups.com.


[sage-support] Re: How do you use SageMath in research, education, ...?

2020-05-24 Thread Matthias Koeppe
On Saturday, May 23, 2020 at 12:18:08 PM UTC-7, Ingo Dahn wrote:
>
> Sounds like an interesting event, what is the intended audience? 
> Developers? Researchers? Educators?
>

All of the above. We have added some more information at 
https://wiki.sagemath.org/days109
 

> Specific times/tracks for each? 
>

Yes, we will announce a detailed program shortly.
 

> Are there reports from previous events? An Agenda? Will there be records 
> of presentations?
>

Previous SageDays (https://wiki.sagemath.org/Workshops) were in-person 
events. This is the first fully virtual event. We plan to record and make 
available presentations (when the presenters give us permission to do so.)

Matthias

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/20f8c18e-ee46-4d53-9de3-3ea9eb096298%40googlegroups.com.


[sage-support] How do you use SageMath in research, education, ...?

2020-05-22 Thread Matthias Koeppe
OK, I know how *I* use SageMath.

But how do *you* use it? Let us know in the online SageMath User Forum.

This is one of the activities of next week's *Global Virtual SageDays 109*, 
a 50-hour virtual event held May 27–29, 2020.

Preliminary information and registration at 
https://wiki.sagemath.org/days109


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/c636b6af-eda1-498e-a2a9-63829532073e%40googlegroups.com.


[sage-support] Re: equation solution in integer

2020-04-17 Thread Matthias Koeppe
http://doc.sagemath.org/html/en/reference/discrete_geometry/sage/geometry/polyhedron/base.html#sage.geometry.polyhedron.base.Polyhedron_base.integral_points

On Friday, April 17, 2020 at 11:16:30 AM UTC-7, Bert Henry wrote:
>
> I tried it with
> var('x, y')
> assume(x,"integer")
> assume(x>0)
> assume(y, "integer")
> assume(y>0)
> solve(x+y==15,x,y)
>
> The result was
>
> (t_0, -t_0 + 15)
>
> obviously right, but not 6,9 7,8 8,7 and 9,6
>
>
>
> Am Freitag, 17. April 2020 19:17:12 UTC+2 schrieb Bert Henry:
>>
>> I have the equation
>> x + y = 15
>> an I'm looking for solution only in the range x=1..9 and y=1..9, x and y 
>> both integer
>> Is there a sage-command to do that?
>>
>> Thanks in advance
>> Bert Henry
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/7982d779-c4d9-4e3a-8f81-a84540c05a07%40googlegroups.com.


Re: [sage-support] Building on Catalina

2020-04-09 Thread Matthias Koeppe
On Thursday, April 9, 2020 at 6:35:53 AM UTC-7, David Einstein wrote:
>
> I did a brew install pkg-config and was notified that version 0.29.1 was 
> already installed, but I could upgrade to 0.29.2, so I did so. Then did a 
> `make distclean` and then make and got marginally further.  Now it dies 
> starting to build sagelib
>
>>

>From the config.log that you posted it seems that you are running configure 
from inside `sage -sh` or you have set PATH manually to include the 
following:
PATH: /Users/davideinstein/projects/sage/build/bin

PATH: /Users/davideinstein/projects/sage/src/bin
PATH: /Users/davideinstein/projects/sage/local/bin


This is not supported. configure should be run outside of `sage -sh` and 
without such PATH settings.
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/13e18e2b-c73c-4ea4-9cdd-b326bf4e72c3%40googlegroups.com.


Re: [sage-support] Sage Crash report

2020-04-08 Thread Matthias Koeppe
On Wednesday, April 8, 2020 at 8:01:38 PM UTC-7, hbetx9 wrote:
>
> No, I just want all users to have this at default. Where should I put the 
> SAGE_ROOT directory? /usr/local? 
>

Use "./configure --prefix=/usr/local/opt/sage-9.0" to set the installation 
prefix (SAGE_LOCAL).


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/394ece00-bd5a-4ac2-9e2f-257fd84999c3%40googlegroups.com.


Re: [sage-support] Sage Crash report

2020-04-08 Thread Matthias Koeppe
Read https://doc.sagemath.org/html/en/developer/ if you wish to make 
changes to Sage, and https://trac.sagemath.org/ticket/29379 for the change 
ticket that makes the upgrade to R 3.6.3


On Wednesday, April 8, 2020 at 3:02:01 PM UTC-7, hbetx9 wrote:
>
> I _almost_ got this to work, I have R 3.6.3 but still get the following 
> error:
>
> * package: r-3.6.2
>   log file: /home/lmiller/sage-9.0/logs/pkgs/r-3.6.2.log
>   build directory: /home/lmiller/sage-9.0/local/var/tmp/sage/build/r-3.6.2
>
> Presumably, there is a flag or configure I can send make to use 3.6.3 
> correct? 
>
>
> After all this is addressed, how to make this available system wide? Is 
> there a script in the SAGE_LOCAL that will do it? I know that's a basic 
> question but I'm curious. I removed Sage 8 so there should be no conflict.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/5a3ec927-0f24-4e0f-951f-aa643386d033%40googlegroups.com.


[sage-support] Re: hyperplane arrangements raises error on regions

2020-02-03 Thread Matthias Koeppe
Try if it works if you use rationals (-48/100) instead of floats (-0.48).

On Monday, February 3, 2020 at 8:48:34 AM UTC-5, Murad Tukan wrote:
>
> Dear all,
>
> Computer info:
> CPU: i7-6500U @ 2.50GHZ
> Memory: 16.0GB
>
> Sage information: SageMath 9.0 (Windows, installed using the .exe file), 
> and even on Linux version.
>
> Platforms ran at: SageMath 9.0 Shell, SageMath 9.0 Notebook, From Python 
> script (and then running the command sage -python "script_name.py").
>
> Description of problem:
>
> When running the following code:
>
> P = [[-0.48,  0.83], [-5.33,  9.23]]
> Q = [[0.43, 0.], [9.04, 0.]]
> Z =  [[-0.35, -0.60], [-1.44, -2.49]]
>
> V = VoronoiDiagram(P)
> R = [r for r in V.regions().items()]
> s = R[0][1].hyperplane_arrangement()
>
> V = VoronoiDiagram(Q)
> R = [r for r in V.regions().items()]
> s = s.add_hyperplane(R[0][1].hyperplane_arrangement())
>
> V = VoronoiDiagram(Z)
> R = [r for r in V.regions().items()]
> s = s.add_hyperplane(R[0][1].hyperplane_arrangement())
>
> s.regions()
>
> Sage fails to compute the regions which is weird since it can compute the 
> vertices which means that there is even a bounded region (in my case). When 
> running the same code on SageMathCell , 
> It is computed smoothly while on my machine it is not!
>
> The full traceback I get is:
>
> ---
> ValueErrorTraceback (most recent call last)
>  in ()
> > 1 s.regions()
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/misc/cachefunc.pyx 
> in sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__ 
> (build/cythonized/sage/misc/cachefunc.c:12712)()
>2308 if self.cache is None:
>2309 f = self.f
> -> 2310 self.cache = f(self._instance)
>2311 return self.cache
>2312
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/geometry/hyperplane_arrangement/arrangement.py
>  
> in regions(self)
>1608 R = self.base_ring()
>1609 dim = self.dimension()
> -> 1610 universe = Polyhedron(eqns=[[0] + [0] * dim], base_ring=R)
>1611 regions = [universe]
>1612 for hyperplane in self:
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/geometry/polyhedron/constructor.py
>  
> in Polyhedron(vertices, rays, lines, ieqs, eqns, ambient_dim, base_ring, 
> minimize, verbose, backend)
> 660 if got_Vrep:
> 661 Vrep = [vertices, rays, lines]
> --> 662 return parent(Vrep, Hrep, convert=convert, verbose=verbose)
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/structure/parent.pyx 
> in sage.structure.parent.Parent.__call__ 
> (build/cythonized/sage/structure/parent.c:9245)()
> 900 return mor._call_(x)
> 901 else:
> --> 902 return mor._call_with_args(x, args, kwds)
> 903
> 904 raise TypeError(_LazyString(_lazy_format, ("No conversion 
> defined from %s to %s", R, self), {}))
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/structure/coerce_maps.pyx
>  
> in sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args 
> (build/cythonized/sage/structure/coerce_maps.c:5081)()
> 178 print(type(C), C)
> 179 print(type(C._element_constructor), 
> C._element_constructor)
> --> 180 raise
> 181
> 182
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/structure/coerce_maps.pyx
>  
> in sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args 
> (build/cythonized/sage/structure/coerce_maps.c:4969)()
> 173 return C._element_constructor(x, *args)
> 174 else:
> --> 175 return C._element_constructor(x, *args, **kwds)
> 176 except Exception:
> 177 if print_warnings:
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/geometry/polyhedron/parent.py
>  
> in _element_constructor_(self, *args, **kwds)
> 523 if convert and Vrep:
> 524 Vrep = [convert_base_ring(_) for _ in Vrep]
> --> 525 return self.element_class(self, Vrep, Hrep, **kwds)
> 526 if nargs == 1 and is_Polyhedron(args[0]):
> 527 polyhedron = args[0]
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/geometry/polyhedron/backend_cdd.py
>  
> in __init__(self, parent, Vrep, Hrep, **kwds)
> 459 sage: TestSuite(p).run()
> 460 """
> --> 461 Polyhedron_cdd.__init__(self, parent, Vrep, Hrep, **kwds)
>
> /opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/geometry/polyhedron/base.py
>  
> in __init__(self, parent, Vrep, Hrep, **kwds)
> 125 elif Hrep is not None:
> 126 ieqs, eqns = Hrep
> --> 127 self._init_from_Hrepresentation(ieqs, eqns, **kwds)
> 128  

[sage-support] Re: Derivative of functions ...

2018-11-02 Thread Matthias Koeppe
On Friday, November 2, 2018 at 5:44:34 PM UTC-7, Emmanuel Charpentier wrote:
>
> One way to define (something almost the same as) what you want is :
> sage: f=piecewise([((-oo,0),x^3),((0,oo),x^2)],var=x)
> sage: f
> piecewise(x|-->x^3 on (-oo, 0), x|-->x^2 on (0, +oo); x)
> [...] Except for the point 0, for which the piecewise function is not 
> defined :
>
>>
>>
For the half-open interval, one needs to use RealSet constructors:

sage: 
f=piecewise([((-oo,0),x^3),(RealSet.unbounded_above_closed(0),x^2)],var=x)
sage: f
piecewise(x|-->x^3 on (-oo, 0), x|-->x^2 on [0, +oo); x)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


[sage-support] Re: Will there be a sage-8.2 for Mac OS X 10.12.x?

2018-05-11 Thread Matthias Koeppe
Some limited testing of a binary distribution on different OS X versions 
can be done via Travis 
CI. https://github.com/mkoeppe/sage_binary_tester/blob/master/.travis.yml 
(needs updating)

On Friday, May 11, 2018 at 9:56:02 AM UTC-7, Volker Braun wrote:
>
> Our binary most likely works on OSX 10.12, but I don't have any way to 
> test. Feel free to try and report back!
>
> On Friday, May 11, 2018 at 1:44:52 AM UTC+2, Samuel Dupree wrote:
>>
>> I'm presently running Sage-8.1 on a Mac Pro running Mac OS X ver. 
>> 10.12.6 (Sierra). I noticed that a Sage-82. for Mac OS X 10.12 is 
>> missing. Will there be a Sage-8.2 for Mac OS X ver. 10.12? 
>>
>> Sam Dupree. 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


[sage-support] Re: Anyone ever used sympol from within Sage?

2018-03-26 Thread Matthias Koeppe
On Tuesday, March 20, 2018 at 1:53:49 PM UTC-7, kcrisman wrote:
>
> I think that people are more often using polymake and/or LattE from within 
> Sage nowadays ... I found out about SymPol (
> https://www.geometrie.uni-rostock.de/software/) today, has anyone worked 
> on a potential interface for that?  I do realize this is probably 
> abandonware to some extent, so just curious, thanks!
>
>  
Polymake has an interface to Sympol 
(https://polymake.org/doku.php/external_software; see 
https://trac.sagemath.org/ticket/20907), so you might be able to use it via 
the Sage polymake interface.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.