Le 10/01/2019 à 22:03, Jeroen Demeyer a écrit :
On 2019-01-10 21:51, 'Julien Puydt' via sage-devel wrote:
Didn't François mention changing SAGE_ROOT wasn't needed?
He said
SAGE_ROOT should only be needed for the packaging system
and possibly the doctests. I regard any needs for SAGE_ROOT at r
> On 11/01/2019, at 09:48, Jeroen Demeyer wrote:
>
> On 2019-01-10 20:46, 'Julien Puydt' via sage-devel wrote:
>>
>>
>> Le 10/01/2019 à 20:07, François Bissey a écrit :
>>> I have recently made the following change in sage-on-gentoo’s env.py
>>> _add_variable_or_fallback('SAGE_LOCAL',
On 2019-01-10 21:51, 'Julien Puydt' via sage-devel wrote:
Didn't François mention changing SAGE_ROOT wasn't needed?
He said
SAGE_ROOT should only be needed for the packaging system
and possibly the doctests. I regard any needs for SAGE_ROOT at runtime
a bug.
In other words: it is still neede
Hi,
Le 10/01/2019 à 21:48, Jeroen Demeyer a écrit :
On 2019-01-10 20:46, 'Julien Puydt' via sage-devel wrote:
Perhaps upstream would accept such a trivial change?
If you make a ticket for it, sure. But it won't help with SAGE_ROOT.
Didn't François mention changing SAGE_ROOT wasn't needed?
On 2019-01-10 20:46, 'Julien Puydt' via sage-devel wrote:
Le 10/01/2019 à 20:07, François Bissey a écrit :
I have recently made the following change in sage-on-gentoo’s env.py
_add_variable_or_fallback('SAGE_LOCAL', sysconfig.get_config_var("prefix”))
which means SAGE_LOCAL is now pulled
Le 10/01/2019 à 20:07, François Bissey a écrit :
I have recently made the following change in sage-on-gentoo’s env.py
_add_variable_or_fallback('SAGE_LOCAL', sysconfig.get_config_var("prefix”))
which means SAGE_LOCAL is now pulled from the system rather than
a seeded value (as it was bef
> On 11/01/2019, at 05:04, E. Madison Bray wrote:
>
> If you want to look-before-you-leap you could also check if
> `SAGE_ROOT` and `SAGE_LOCAL` are set to something reasonable in
> `os.environ`.
Just SAGE_LOCAL. SAGE_ROOT should only be needed for the packaging system
and possibly the docte
On Thursday, January 10, 2019 at 9:58:56 AM UTC-6, E. Madison Bray wrote:
>
> > On archlinux that also uses system Python for Sage the
> > situation is better: importing sage.all in Python2 does work! Even
> > though the configuration constants are not in the environment! They
> > are set up pro
On Thursday, January 10, 2019 at 9:38:15 AM UTC-6, vdelecroix wrote:
>
> Could you repeat the order in which things are broken.
>
Any of the following sequences of commands will install both the SnapPy
Python package and SageMath without producing any errors:
0) install python2 and python-pip
On Thu, Jan 10, 2019 at 4:47 AM Nathan Dunfield wrote:
>
> I am a developer of the Python package "snappy" which acquires extra features
> when imported inside of Sage. Some of our Linux users have recently reported
> difficulties with SnapPy on machines where Sage was installed by the standard
On Thu, Jan 10, 2019 at 1:57 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> (side note)
>
> On archlinux that also uses system Python for Sage the
> situation is better: importing sage.all in Python2 does work! Even
> though the configuration constants are not in the environment! They
Le 10/01/2019 à 16:01, Nathan Dunfield a écrit :
On Thursday, January 10, 2019 at 6:47:33 AM UTC-6, vdelecroix wrote:
Le 10/01/2019 à 04:47, Nathan Dunfield a écrit :
P.S. In the Debian package "sage" does not accept the "-pip" flag, even
though installing the "sagemath" package does pull
On Thursday, January 10, 2019 at 6:47:33 AM UTC-6, vdelecroix wrote:
>
> Le 10/01/2019 à 04:47, Nathan Dunfield a écrit :
> >
> > P.S. In the Debian package "sage" does not accept the "-pip" flag, even
> > though installing the "sagemath" package does pull in "pip" (tested on a
> > clear Sid
(side note)
On archlinux that also uses system Python for Sage the
situation is better: importing sage.all in Python2 does work! Even
though the configuration constants are not in the environment! They
are set up properly in sage_env.py that is part of the SageMath
installation. And more precisel
Le 10/01/2019 à 04:47, Nathan Dunfield a écrit :
P.S. In the Debian package "sage" does not accept the "-pip" flag, even
though installing the "sagemath" package does pull in "pip" (tested on a
clear Sid Docker container). Why is this? I ask because our current
instructions for installing Snap
Dear Nathan,
I think that the cause of the trouble is that in Debian if you
start Python and try "import sage" it will fail. You first need
to set up some environment variables via
$ source /usr/share/sagemath/bin/sage-env
Best
Vincent
PS: I ran into that with surface_dynamics
https://gitlab.c
I've forwarded this to sage-packaging, and the relevant Debian list,
as more appropriate forums for this issue.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sag
I am a developer of the Python package "snappy" which acquires extra
features when imported inside of Sage. Some of our Linux users have
recently reported difficulties with SnapPy on machines where Sage was
installed by the standard package manger making use of the system libraries
and in parti
18 matches
Mail list logo
