> On 21/11/2018, at 03:52, Jeroen Demeyer wrote:
>
> On 2018-11-06 19:07, François Bissey wrote:
>> SAGE_LOCAL is another story,
>> however we probably could figure it out from the python configuration rather
>> than a seed.
>
> Isn't SAGE_LOCAL == sys.prefix
Should be. But following this
On Fri, Nov 16, 2018 at 2:38 PM Luca De Feo wrote:
>
> > How fast will new SageMath versions be packaged? I suppose that fast
> > enought, and those needing the bleeding edge version can compile it
> > themself.
>
> I agree. Ubuntu bionic has 8.1, cosmic has 8.3.
>
> Unless we screw up and make
On 2018-11-06 19:07, François Bissey wrote:
SAGE_LOCAL is another story,
however we probably could figure it out from the python configuration rather
than a seed.
Isn't SAGE_LOCAL == sys.prefix
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
> I guess that 50 simultaneous connection will be the maximum. The use might
> be, for example, a course on graph theory having mandatory but trivial
> exercise about SageMath graph functions.
That's a reasonable load.
--
You received this message because you are subscribed to the Google Groups
On Fri, 16 Nov 2018, Luca De Feo wrote:
and maybe 10 of them will be heavy duty users. Then maybe 500 may
be users in some random course, or checking just one computation etc.
500 hundred simultaneous connections may also be a bit too much,
depending on how powerful your server is.
I guess
> How fast will new SageMath versions be packaged? I suppose that fast
> enought, and those needing the bleeding edge version can compile it
> themself.
I agree. Ubuntu bionic has 8.1, cosmic has 8.3.
Unless we screw up and make Sage impossible to package (see mail by
Samuel on Debian freeze),
On Mon, 5 Nov 2018, Luca De Feo wrote:
Packagers have already solved it for various distributions, so, if you
don't need a Sage version compiled from sources, you can have a
working Sage + JupyterHub setup using the system packages with no
further hacks.
How fast will new SageMath versions be
> On 7/11/2018, at 01:12, Erik Bray wrote:
>
> I'm not necessary suggesting a full replacement: Just a dumb config in
> addition to it that can be used both from sage.env and perhaps
> sage-env as well. I tossed about some ideas for this in
> https://trac.sagemath.org/ticket/22652 and
Hi,Le 6 nov. 2018 13:57, Timo Kaufmann a écrit :> I think the one "new" point I'm
making here is that `import sage` should *just work* without having to
set any special environment variables :/I very much agreeMore precisely : it should be possible to tweak the environment so sage can run from a
> I think the one "new" point I'm
making here is that `import sage` should *just work* without having to
set any special environment variables :/
I very much agree
On Tue, Nov 6, 2018 at 1:12 PM Erik Bray wrote:
> On Tue, Nov 6, 2018 at 1:00 PM Timo Kaufmann wrote:
> >
> > I've had similar
On Tue, Nov 6, 2018 at 1:00 PM Timo Kaufmann wrote:
>
> I've had similar thoughts for a while. Replacing sage-env with a dumb config
> file that can be parsed from within python would go a long way. I'm not too
> familiar with the native sage-env however, it might do some clever stuff that
> a
I've had similar thoughts for a while. Replacing sage-env with a dumb
config file that can be parsed from within python would go a long way. I'm
not too familiar with the native sage-env however, it might do some clever
stuff that a dumb config file couldn't do.
Am Dienstag, 6. November 2018
On Mon, Nov 5, 2018 at 8:11 AM Jori Mäntysalo wrote:
>
> I am trying to marry SageMath and Jupyterhub. I think I got them engaged,
> but the wedding night has a problem:
>
> Error: You must set the SAGE_ROOT environment variable or run this
> script from the SAGE_ROOT or SAGE_ROOT/local/bin/
I tried your solution, it didn't work for me. In jupyter the kernel did not
start, in jupyterlab there was also some style issues.
El lunes, 5 de noviembre de 2018, 14:56:50 (UTC+1), Enrique Artal escribió:
>
> That's true. I just edit the kernel.json for each new release (I read it
> in some
> I am trying to marry SageMath and Jupyterhub. I think I got them engaged,
> but the wedding night has a problem:
This is not a Sage + JupyterHub problem as much as a Sage + system Jupyter one.
Packagers have already solved it for various distributions, so, if you
don't need a Sage version
That's true. I just edit the kernel.json for each new release (I read it in
some tutorial for jupyterhub+sagemath). I will try this.
El lunes, 5 de noviembre de 2018, 10:20:59 (UTC+1), Kwankyu Lee escribió:
>
> The
>
> On Monday, November 5, 2018 at 5:53:35 PM UTC+9, Jori Mäntysalo wrote:
>>
>>
The
On Monday, November 5, 2018 at 5:53:35 PM UTC+9, Jori Mäntysalo wrote:
>
> On Mon, 5 Nov 2018, Enrique Artal wrote:
>
> > For me it works adding "env": { "SAGE_ROOT": "where_SAGE_ROOT_is" } in
> > kernel.json
>
> Thanks, seems to be much better solution.
A problem with this is that it
On Mon, 5 Nov 2018, Enrique Artal wrote:
For me it works adding "env": { "SAGE_ROOT": "where_SAGE_ROOT_is" } in
kernel.json
Thanks, seems to be much better solution.
Now, what is the best practise for upgrading Sage? Jupyterhub makes it
easy to have several kernels installed, but there is
For me it works adding "env": { "SAGE_ROOT": "where_SAGE_ROOT_is" } in
kernel.json
El lunes, 5 de noviembre de 2018, 8:21:31 (UTC+1), François Bissey escribió:
>
> Didn’t we have that conversation a couple of months ago?
> The message here comes from this section of code in sage-env
>
> # New
On Mon, 5 Nov 2018, François Bissey wrote:
I’d be curious about that, but yes that may be off-list.
Of course if I can make a good step-by-step manual, then I will write
about that in this list.
--
Jori Mäntysalo
I’d be curious about that, but yes that may be off-list.
François
> On 5/11/2018, at 20:42, Jori Mäntysalo wrote:
>
> Now it's time for polyamory, i.e. getting also shibboleth ready. But that
> will be off-topic for this list.
--
You received this message because you are subscribed to the
On Mon, Nov 5, 2018 at 7:42 AM Jori Mäntysalo wrote:
>
> On Mon, 5 Nov 2018, François Bissey wrote:
>
> > Didn’t we have that conversation a couple of months ago?
> > The message here comes from this section of code in sage-env
>
> > else
> ># No idea what SAGE_ROOT should be...
> >echo
On Mon, 5 Nov 2018, François Bissey wrote:
Didn’t we have that conversation a couple of months ago?
The message here comes from this section of code in sage-env
else
# No idea what SAGE_ROOT should be...
echo >&2 "Error: You must set the SAGE_ROOT environment variable or run this"
Didn’t we have that conversation a couple of months ago?
The message here comes from this section of code in sage-env
# New value for SAGE_ROOT: either SAGE_ROOT (if given)
# or a guessed value based on pwd.
if [ -n "$SAGE_ROOT" ]; then
NEW_SAGE_ROOT="$SAGE_ROOT"
elif [ -f sage -a -d build ];
I am trying to marry SageMath and Jupyterhub. I think I got them engaged,
but the wedding night has a problem:
Error: You must set the SAGE_ROOT environment variable or run this
script from the SAGE_ROOT or SAGE_ROOT/local/bin/ directory.
Error setting environment variables by sourcing
25 matches
Mail list logo
