Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Jori Mäntysalo
On Thu, 24 Aug 2017, kcrisman wrote: OK. What packages or parts have been updated lately? See perhaps https://trac.sagemath.org/ticket/22431 or https://trac.sagemath.org/ticket/23066 though I don't see immediately which packages were upgraded there.  #22431 is a new ticket, but

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Jori Mäntysalo
On Thu, 24 Aug 2017, Dima Pasechnik wrote: sagenb is installed by pip, which pulls packages from the net; whatever comes up as the "stable" version,gets installed. We used to pin down versions, but don't do this any more. You can look at the output of  ./sage --pip list to see what versions

[sage-devel] why does starting sage take twice as long as importing sage?

2017-08-24 Thread William Stein
Puzzle:Why does it take nearly **twice as long** to just run sage and exit as it does to import the sage library and run a command?Timings below are on an SSD: ~$ time sage -python -c "import sage.all; sage.all.factor(2018)" real

Re: [sage-devel] Re: python3 in sage

2017-08-24 Thread John H Palmieri
On Thursday, August 24, 2017 at 2:50:09 PM UTC-7, William wrote: > > On Thu, Aug 24, 2017 at 2:17 PM, Nils Bruin > wrote: > > On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote: > >> > >> I'm not sure what the status is these days, but we may want to stop > >>

Re: [sage-devel] Re: python3 in sage

2017-08-24 Thread William Stein
On Thu, Aug 24, 2017 at 2:17 PM, Nils Bruin wrote: > On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote: >> >> I'm not sure what the status is these days, but we may want to stop >> including a python3 binary in Sage by default with "python3" right >> there in the

[sage-devel] Re: python3 in sage

2017-08-24 Thread Nils Bruin
On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote: > > I'm not sure what the status is these days, but we may want to stop > including a python3 binary in Sage by default with "python3" right > there in the "sage -sh" path... As far as I understand, having python3 included in

[sage-devel] python3 in sage

2017-08-24 Thread William Stein
Hi, I'm not sure what the status is these days, but we may want to stop including a python3 binary in Sage by default with "python3" right there in the "sage -sh" path... It randomly and confusingly breaks a lot of stuff related to Jupyter kernels getting installed into Sage. You can observe

[sage-devel] sage-support moderation?

2017-08-24 Thread Dima Pasechnik
Do you volunteer to weed out spam? :) -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email

[sage-devel] sage-support moderation?

2017-08-24 Thread kcrisman
Has the time come for sage-support to allow posts by non-members? Some questions are not ideal for the Q format of ask.sagemath but we don't necessarily want to ask people to have to wait for signing up on sage-support ... or waiting for approval as members to ask a simple question. See

Re: [sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-24 Thread Erik Bray
On Thu, Aug 24, 2017 at 4:45 PM, Jeroen Demeyer wrote: > On 2017-08-23 23:44, Marc Masdeu wrote: >> >> This is essentially what they are supposed to be. > > > But it's not what your package does! You are using "sage" all over the > place. I'm probably missing something,

Re: [sage-devel] Help with Expect interface UnicodeEncodeError for Julia interface

2017-08-24 Thread Erik Bray
On Thu, Aug 24, 2017 at 3:43 PM, mforets wrote: > > Hi Erik, > OK thanks for the link, I will go ahead with PyJulia. > > I think the problem is the returned times symbol, which is a fancy "x", and > that one requires Python 3 to be properly parsed. To be clear, that doesn't

Re: [sage-devel] Template (cookiecutter) for easily distributing SageMath code

2017-08-24 Thread Jeroen Demeyer
On 2017-08-23 23:44, Marc Masdeu wrote: This is essentially what they are supposed to be. But it's not what your package does! You are using "sage" all over the place. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Dima Pasechnik
sagenb is installed by pip, which pulls packages from the net; whatever comes up as the "stable" version, gets installed. We used to pin down versions, but don't do this any more. You can look at the output of ./sage --pip list to see what versions you have. Sagenb explicitly needs the

Re: [sage-devel] Help with Expect interface UnicodeEncodeError for Julia interface

2017-08-24 Thread mforets
Hi Erik, OK thanks for the link, I will go ahead with PyJulia. I think the problem is the returned times symbol, which is a fancy "x", and that one requires Python 3 to be properly parsed. El jueves, 24 de agosto de 2017, 11:59:00 (UTC+2), Erik Bray escribió: > > On Wed, Aug 23, 2017 at 6:33

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread kcrisman
On Thursday, August 24, 2017 at 4:54:48 AM UTC-4, Jori Mäntysalo wrote: > > On Thu, 24 Aug 2017, Dima Pasechnik wrote: > > > although it very well might be due to its dependencies, like flask, > > etc., updated to newer versions, e.g. for the purpose of python3 > > compatibility. > > OK.

Re: [sage-devel] Help with Expect interface UnicodeEncodeError for Julia interface

2017-08-24 Thread Erik Bray
On Wed, Aug 23, 2017 at 6:33 PM, mforets wrote: > Hello, > I'm writing an "expect" interface to use Julia from Sage, copy pasted from > the Matlab `interfaces/matlab.py`. > > For the moment, the code is here: > https://gist.github.com/mforets/26d42220946fba8f8e1feb8208783231 >

Re: [sage-devel] Re: Template (cookiecutter) for easily distributing SageMath code

2017-08-24 Thread Erik Bray
On Wed, Aug 23, 2017 at 5:56 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > One thing (IMHO much more important than the "cookie cutter" buisness) is to > actually have a community supported language for SageMath in travis [1]. My > aim is to allow the following in the travis script

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Jori Mäntysalo
On Thu, 24 Aug 2017, Dima Pasechnik wrote: although it very well might be due to its dependencies, like flask, etc., updated to newer versions, e.g. for the purpose of python3 compatibility. OK. What packages or parts have been updated lately? -- Jori Mäntysalo

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Dima Pasechnik
although it very well might be due to its dependencies, like flask, etc., updated to newer versions, e.g. for the purpose of python3 compatibility. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Dima Pasechnik
check out the upstream sagenb repo and do git blame, indeed. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-08-24 Thread Jori Mäntysalo
Is there an easy way to see what has been done in .../sage/local/lib/python2.7/site-packages/flask/ and in .../sage/local/lib/python2.7/site-packages/sagenb/flask_version/ between version 8.0 and the one before it? Something like git blame? With Google I found for example