[sage-support] Re: Failure to compile Sage 10.3.rc0

2024-02-26 Thread Antonio Rojas
Sage doesn't currently support flint 3.1. Either build with the bundled 
flint or patch [1] sagelib

[1] https://aur.archlinux.org/cgit/aur.git/tree/flint-3.1.patch?h=sagemath-git

El lunes, 26 de febrero de 2024 a las 15:50:40 UTC+1, Peter Mueller 
escribió:

> Installation of Sage 10.3.rc0 from source on an up-to-date Arch Linux 
> machine fails. I'm not sure if the following snippet of the log file hints 
> to the problem:
>
> [sagelib-10.3.rc0] In file included from 
> sage/symbolic/ginac/pseries.cpp:26:
> [sagelib-10.3.rc0] sage/symbolic/ginac/useries-flint.h:31:11: error: 
> 'fmpq_init_set_mpz_frac_readonly' is deprecated.
> [sagelib-10.3.rc0]31 | extern "C" void 
> fmpq_init_set_mpz_frac_readonly(fmpq_t z, const mpz_t p, const mpz_t q);
> [sagelib-10.3.rc0]   |   
> ^~
> [sagelib-10.3.rc0] sage/symbolic/ginac/useries-flint.h:31:55: error: 
> expected ')' before 'z'
> [sagelib-10.3.rc0]31 | extern "C" void 
> fmpq_init_set_mpz_frac_readonly(fmpq_t z, const mpz_t p, const mpz_t q);
> [sagelib-10.3.rc0]   | 
>~  ^~
> [sagelib-10.3.rc0]   | 
>   )
>

-- 
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/3c1404e0-20ac-4fc2-b761-0918c870543cn%40googlegroups.com.


[sage-support] Re: Failed 14 tests after building from source

2023-08-11 Thread Antonio Rojas


El viernes, 11 de agosto de 2023 a las 19:37:02 UTC+2, Abheet Chaudhary 
escribió:


What should I do?


Nothing, these are all known issues caused by new versions of gmp, singular 
and glibc
 There are pull requests to fix most of them already.

-- 
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/900ef1ea-026b-485c-a473-f4bc51203b56n%40googlegroups.com.


[sage-support] Re: Question about a deprecation warning

2020-07-01 Thread Antonio Rojas


El miércoles, 1 de julio de 2020, 21:06:43 (UTC+2), John H Palmieri 
escribió:
>
>
> Why so many deprecation warnings? I think they're coming from plain 
> Python; why doesn't Python print the warnings?
>
>
>
Because python ignores deprecation 
warnings, 
https://docs.python.org/3/library/warnings.html#default-warning-filter 

-- 
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/af97136d-eeea-4003-9175-23224915fb3bo%40googlegroups.com.


[sage-support] Re: PackageNotFoundError: cblas not found

2019-07-24 Thread Antonio Rojas


El miércoles, 24 de julio de 2019, 15:33:02 (UTC+2), John Robson escribió:
>
>
> How can I inform to sage to use the cblas from openblas-lapack?
>
>
You need to provide a cblas.pc file in /usr/lib/pkgconfig/ so that 
pkgconfig can detect the library. Something like

libdir=/usr/lib
includedir=/usr/include

Name: CBLAS
Description: C Standard Interface to BLAS Basic Linear Algebra Subprograms
Version: 3.8.0
URL: http://www.netlib.org/blas/#_cblas
Libs: -L${libdir} -lcblas
Cflags: -I${includedir}
Requires.private: blas

 

-- 
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/e259f6e4-1847-4d93-a9df-6173ac8cfad9%40googlegroups.com.


Re: [sage-support] Re: Sage options not recognized.

2019-03-31 Thread Antonio Rojas
You are still running sage from the debian repo. You need to run ./sage 
from the dir where you installed the sage binary (or add such dir to your 
PATH)

El domingo, 31 de marzo de 2019, 15:29:04 (UTC+2), Jose Garcia escribió:
>
> Thank you for the response. I tried installing Sage from Binary and it was 
> successful.
>
> However, i still get error messages when trying to run the commands to 
> install this optional package i keep talking about.
>
> sage --package fix-checksum conjecturing
> sage-run received unknown option: --package
> usage: sage [options]
> Try 'sage -h' for more information.
>
>>
>>

-- 
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: how to fix sage-crash?

2019-03-04 Thread Antonio Rojas
You are mixing a system-wide Sage install with a user-installed ipython - 
this is really calling for trouble. Fix your python paths.

El lunes, 4 de marzo de 2019, 11:42:47 (UTC+1), Reynier de la Cruz escribió:
>
> ***
>
> IPython post-mortem report
>
> {'commit_hash': u'033ab93c7',
>  'commit_source': 'installation',
>  'default_encoding': 'UTF-8',
>  'ipython_path': 
> '/home/antonio/.local/lib/python2.7/site-packages/IPython',
>  'ipython_version': '5.8.0',
>  'os_name': 'posix',
>  'platform': 'Linux-4.15.0-39-generic-x86_64-with-Ubuntu-18.04-bionic',
>  'sys_executable': '/usr/bin/python',
>  'sys_platform': 'linux2',
>  'sys_version': '2.7.15rc1 (default, Nov 12 2018, 14:31:15) \n[GCC 7.3.0]'}
>
> ***
>
>
>
> ***
>
> Crash traceback:
>
> ---
> ---
> SyntaxError   Python 2.7.15rc1: /usr/bin/python
>Mon Mar  4 02:52:33 2019
> A problem occurred executing Python code.  Here is the sequence of function
> calls leading up to the error, with the most recent (innermost) call last.
> /usr/share/sagemath/bin/sage-ipython in ()
>   1 #!/usr/bin/env python
>   2 # -*- coding: utf-8 -*-
>   3 """
>   4 Sage IPython startup script.
>   5 """
>   6 
>   7 from sage.repl.interpreter import SageTerminalApp
>   8 
>   9 app = SageTerminalApp.instance()
> ---> 10 app.initialize()
> global app.initialize =  of >
>  11 app.start()
>
> 
>  
> in initialize(self=, 
> argv=None)
>
> /home/antonio/.local/lib/python2.7/site-packages/traitlets/config/application.pyc
>  
> in catch_config_error(method=, 
> app=, *args=(None,), 
> **kwargs={})
>  72 TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR = False
>  73 else:
>  74 raise ValueError("Unsupported value for environment variable: 
> 'TRAITLETS_APPLICATION_RAISE_CONFIG_FILE_ERROR' is set to '%s' which is 
> none of  {'0', '1', 'false', 'true', ''}."% _envvar )
>  75 
>  76 
>  77 @decorator
>  78 def catch_config_error(method, app, *args, **kwargs):
>  79 """Method decorator for catching invalid config 
> (Trait/ArgumentErrors) during init.
>  80 
>  81 On a TraitError (generally caused by bad config), this will 
> print the trait's
>  82 message, and exit the app.
>  83 
>  84 For use on init methods, to prevent invoking excepthook on 
> invalid input.
>  85 """
>  86 try:
> ---> 87 return method(app, *args, **kwargs)
> method = 
> app =  0x7fccfb9e8390>
> args = (None,)
> kwargs = {}
>  88 except (TraitError, ArgumentError) as e:
>  89 app.print_help()
>  90 app.log.fatal("Bad config encountered during 
> initialization:")
>  91 app.log.fatal(str(e))
>  92 app.log.debug("Config at the time: %s", app.config)
>  93 app.exit(1)
>  94 
>  95 
>  96 class ApplicationError(Exception):
>  97 pass
>  98 
>  99 
> 100 class LevelFormatter(logging.Formatter):
> 101 """Formatter with additional `highlevel` record
> 102 
>
> /home/antonio/.local/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc 
> in initialize(self=, 
> argv=None)
> 301 
> 302 return super(TerminalIPythonApp, 
> self).parse_command_line(argv)
> 303 
> 304 @catch_config_error
> 305 def initialize(self, argv=None):
> 306 """Do actions after construct, but before starting the 
> app."""
> 307 super(TerminalIPythonApp, self).initialize(argv)
> 308 if self.subapp is not None:
> 309 # don't bother initializing further, starting subapp
> 310 return
> 311 # print self.extra_args
> 312 if self.extra_args and not self.something_to_run:
> 313 self.file_to_run = self.extra_args[0]
> 314 self.init_path()
> 315 # create the shell
> --> 316 self.init_shell()
> self.init_shell =  >
> 317 # and draw the banner
> 318 self.init_banner()
> 319 # Now a variety of things that happen after the banner is 
> printed.
> 320 self.init_gui_pylab()
> 321 self.init_extensions()
> 322 self.init_code()
> 323 
> 324 def init_shell(self):
> 325 """initialize the InteractiveShell instance"""
> 326 # Create an InteractiveShell instance.
> 327 # shell.display_banner should always be False for the 
> terminal
> 328 # ba

Re: [sage-support] plot3d doesn't work in jupyterlab / jupyter notebook

2018-11-18 Thread Antonio Rojas

El domingo, 18 de noviembre de 2018, 4:24:58 (UTC+1), Kolen Cheung escribió:
>
> Currently it's like this: on an ArchLinux machine, install sage through 
> pacman, and install the sagemath kernel to my jupyterlab hub. And then 
> through the jupyterlab-hub I remote it and use the sagemath kernel and 
> typed the above commands.
>
> I'm guessing it requires some widgets to be installed in jupyter for them 
> to work. Since I'm not using the Sage notebook interface but a 
> Jupyterlab-hub instance that has the sagemath kernel installed.
>
> ​
>>>
>>
The three.js version shipped by Arch is too new and not supported by Sage. 
Either use jsmol (which is still the default), or use the online version of 
three.js (viewer='threejs', online=True) (with sagemath 8.4-4, in previous 
versions the online version doesn't work either)

-- 
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.


Re: [sage-support] Info about python3.6+

2018-03-02 Thread Antonio Rojas

El viernes, 2 de marzo de 2018 8:43:50 (CET), Henri Girard escribió:

Hi,
This is the notebook I am running, apparently sage runs with 
python3.6+ , is this exact ?

About Jupyter Notebook


No, that only means the Jupyter notebook is running on Python 3.6. The 
python version of the kernel being run doesn't have to match.


--
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: sage-ipython crashes

2017-06-15 Thread Antonio Rojas
El Thu, 15 Jun 2017 08:31:48 -0700, vincent.herbert escribió:

> After reading last crash report, I saw a problem with sage-maxima.lisp.
> 
> I seached a solution and found this thread
> https://ask.sagemath.org/question/9119/sagecython-compile-embedded-
cython-with-sage-import/
> 
> Then, I just put export SAGE_LOCAL="/usr" in ~/.zshrc and sage works
> fine.

That shouldn't be necessary. Why are you running sage-ipython? You are not 
supposed to call that script directly, the command to run sage is "sage". 
That will set up all necessary env variables and call sage-ipython as 
needed.

-- 
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: sage-ipython crashes

2017-06-14 Thread Antonio Rojas

>>
> Have you some suggestions? Thanks.

Install the official lapack/blas packages from the repositories or rebuild 
whatever unofficial version you're using.


-- 
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.