ATM we're setting it to /usr (arbitrary choice) simply because at some
point Sage refused to start if it wan't set. But setting it to anything
else doesn't make any difference.
El miércoles, 23 de mayo de 2018, 0:02:24 (UTC+2), Nils Bruin escribió:
>
> On Saturday, May 19, 2018 at 12:08:22 AM UT
> On 23/05/2018, at 10:02, Nils Bruin wrote:
>
> On Saturday, May 19, 2018 at 12:08:22 AM UTC-7, Antonio Rojas wrote:
>
>
> OK, so how do we see whether the $SAGE_ROOT/sage script needs to be used?
> Can we just see if $SAGE_ROOT/sage is present and executable and if not, use
> $SAGE_LOCAL
On Saturday, May 19, 2018 at 12:08:22 AM UTC-7, Antonio Rojas wrote:
>
>
>
>> OK, so how do we see whether the $SAGE_ROOT/sage script needs to be
>> used? Can we just see if $SAGE_ROOT/sage is present and executable and if
>> not, use $SAGE_LOCAL/bin/sage? The remark by François seems quite to t
>
> OK, so how do we see whether the $SAGE_ROOT/sage script needs to be used?
> Can we just see if $SAGE_ROOT/sage is present and executable and if not,
> use $SAGE_LOCAL/bin/sage? The remark by François seems quite to the point:
> if sage is installed system-wide as a package of python2, the
On Friday, May 18, 2018 at 11:42:09 PM UTC-7, Antonio Rojas wrote:
>
>
> El sábado, 19 de mayo de 2018, 8:30:12 (UTC+2), Nils Bruin escribió:
>>
>> so, am I right in concluding that distribution packages patch this
>> anyway and that we can therefore safely put $SAGE_ROOT/sage in kernel.json
>>
El sábado, 19 de mayo de 2018, 8:30:12 (UTC+2), Nils Bruin escribió:
>
> so, am I right in concluding that distribution packages patch this anyway
> and that we can therefore safely put $SAGE_ROOT/sage in kernel.json by
> default?
>
No - this does "the right thing" out of the box currently. On
> On 19/05/2018, at 18:30, Nils Bruin wrote:
>
> On Thursday, May 17, 2018 at 1:01:21 AM UTC-7, François Bissey wrote:
> Actually in sage-on-gentoo I reduced that quite a bit. In vanilla we have
> "argv": ["/home/fbissey/sandbox/git-fork/sage-8.3.b0/local/bin/sage",
> "--python", "-m", "sage.
On Thursday, May 17, 2018 at 1:01:21 AM UTC-7, François Bissey wrote:
>
> Actually in sage-on-gentoo I reduced that quite a bit. In vanilla we have
> "argv": ["/home/fbissey/sandbox/git-fork/sage-8.3.b0/local/bin/sage",
> "--python", "-m", "sage.repl.ipython_kernel", "-f", "{connection_file}”]
>
On Thursday, May 17, 2018 at 1:01:21 AM UTC-7, François Bissey wrote:
>
> Actually in sage-on-gentoo I reduced that quite a bit. In vanilla we have
> "argv": ["/home/fbissey/sandbox/git-fork/sage-8.3.b0/local/bin/sage",
> "--python", "-m", "sage.repl.ipython_kernel", "-f", "{connection_file}”]
>
Actually in sage-on-gentoo I reduced that quite a bit. In vanilla we have
"argv": ["/home/fbissey/sandbox/git-fork/sage-8.3.b0/local/bin/sage",
"--python", "-m", "sage.repl.ipython_kernel", "-f", "{connection_file}”]
That is, sage-devs go to quite some lengths to launch sage’s python with the
sag
El jueves, 17 de mayo de 2018, 6:46:11 (UTC+2), Nils Bruin escribió:
>
>
> Are there good reasons to refer to .../local/bin/sage rather than the
> .../sage script? If not, then it might be more flexible to change it.
>
>
This would break distribution packages, where SAGE_LOCAL is generally set
to
11 matches
Mail list logo
