Re: [sage-devel] Terminal Cowsay / Math-Related Fortunes

The website is https://sagedebianlive.metelu.net/ There you can find a link to the source code as well as instructions on how to add things to the key. Vincent Le 25/11/2016 à 00:21, Maxie Schmidt a écrit : Hello. I'm putting together a fortune mod and cowsay figures providing "mathy"

[sage-devel] Terminal Cowsay / Math-Related Fortunes

Hello. I'm putting together a fortune mod and cowsay figures providing "mathy" wisdom and related material. A working version is available in my repository at https://github.com/maxieds/math-fortune-mod.git. I would like to have this software installed on the Sage live boot usb drive images,

Re: [sage-devel] Re: Proposal: move SageNB back to Sage

Emmanuel Charpentier wrote: > 2) In contrast, the Sage notebook, while quite advanced *for its time*, has > remained a Sage-only interface. Yes, you can use a number of other tools > with i, *as long as they are known by Sage*. > This simultaneously enhances and limits its utility. For example,

logging in jupyter notebook [Re: [sage-devel] increasing verbose level for sub-routines]

Dear all, this summer an attempt to use Python's logging module in SageMath for logging/verbosing on https://trac.sagemath.org/ticket/21349 >From the Sage-side this seems to be completed, but the logging does not work well with the jupyter notebook. Is anyone out there, who can help fixing

[sage-devel] Re: [sage-notebook] Re: Proposal: move SageNB back to Sage

On Thu, Nov 24, 2016 at 1:38 AM, Jack Dyson wrote: > Hi William, > installed the docker version - exciting stuff - just brilliant! > thanks. We need this "sagewide" asap really. Be looking into it as I > understand more. > small question when you have a moment: > docker

[sage-devel] Fwd: Big news!!

On Thursday, November 24, 2016 at 12:28:52 PM UTC, Bill Hart wrote: > > Hi all, > > Here is some fantastic news about a huge new grant, part of which will > fund a new Open Source Computer Algebra System for up to 12 years. This is > great news for MPIR, Flint and Nemo, since deep within the

Re: [sage-devel] Re: doctesting external file: import troubles

On 2016-11-24 17:04, Marc Mezzarobba wrote: > Daniel Krenn wrote: >> How to deal with this import problem, so that it works in the jupyter >> notebook and with doctesting? > > Perhaps try something like > > SAGE_PATH=$PWD sage -t something.py Works indeed. Thank you. I am surprised that this

[sage-devel] Re: doctesting external file: import troubles

Daniel Krenn wrote: > How to deal with this import problem, so that it works in the jupyter > notebook and with doctesting? Perhaps try something like SAGE_PATH=$PWD sage -t something.py ? There may be a better way, I don't know. -- Marc -- You received this message because you are

[sage-devel] Re: [sage-notebook] Re: Proposal: move SageNB back to Sage

ok cheers Harald ! On 24 November 2016 at 11:49, Harald Schilly wrote: > > On Thu, Nov 24, 2016 at 10:38 AM, Jack Dyson wrote: >> >> any idea ? > > > > The error is: NoSuchKernel: No such kernel named ir > > That means, that the "ir" kernel for R (and

[sage-devel] Re: Proposal: move SageNB back to Sage

A few random thoughts : 1) the Jupyter notebook is an interface used by a *lot* of projects. Jupyter kernels do exist for a large number of computing tools. It is therefore well-developed and actively maintained. 2) In contrast, the Sage notebook, while quite advanced *for its time*, has

[sage-devel] doctesting external file: import troubles

I have an external (not in the Sage source tree) file something.py which I want to doctest with "sage -t". This file contains an import from __future__ import absolute_import from sub.whatever import whateverblub from a subdirectory. Doctesting yields ImportError: No module named

Re: [sage-devel] Re: Implements change_ring() for BooleanPolynomialRing (#21817) -- Needs Review

Hi On 23/11/2016 3:53 PM, Simon King wrote: > Hi, > > On 2016-11-22, Rusydi H. Makarim wrote: >>> Shouldn't it raise an error as soon as the "new" base ring is different >>> from GF(2)? >>> Apparently restricting base_ring only for GF(2) causes some test failures

[sage-devel] Re: [sage-notebook] Re: Proposal: move SageNB back to Sage

On Thu, Nov 24, 2016 at 10:38 AM, Jack Dyson wrote: > any idea ? ​The error is: NoSuchKernel: No such kernel named ir ​ That means, that the "ir" kernel for R (and many others) aren't available in that image. I mean, you're running a local version of smc with some

Re: [sage-devel] requirements for publishing (reference request)

thank :) On Wednesday, November 23, 2016 at 10:24:11 PM UTC+2, Justin C. Walker wrote: > > Dear Hezi, > > > On Nov 23, 2016, at 03:39 , Hezi Halawi > wrote: > > > > Dear all, > > > > I am writing a code in sage about automorphic representations and > Eisenstein

[sage-devel] Re: [sage-notebook] Re: Proposal: move SageNB back to Sage

Hi William, installed the docker version - exciting stuff - just brilliant! thanks. We need this "sagewide" asap really. Be looking into it as I understand more. small question when you have a moment: docker starts correctly, everything works-I have SMC locally but I can't get in sage dedicated

Re: [sage-devel] Re: [sage-notebook] Re: Proposal: move SageNB back to Sage

On Wed, Nov 23, 2016 at 03:54:18PM -0800, Eric Gourgoulhon wrote: >Actually, since version 7.3, Sage is shipped with a migration tool >sagenb --> Jupyter, developed by Volker (cf. #19877). Indeed! Thanks you (and Jeroen as well) for making my mentions more explicit. For a smooth