Jori,
sorry for crying out loud, but noone is going to work on sagenb, besides
maybe you, I think.
Messing around with 11 years old web technology is very hard indeed.
What exactly are you missing from jupyter nb, or jupyter hub, or some
version of SMC
people managed to get running on their int
On Wed, 6 Sep 2017, kcrisman wrote:
I suspect perhaps
https://github.com/sagemath/sagenb/commit/9dd5c0f8c783de7cb0ae21c9f445ab8260b5a0ac
is the culprit, and
put something on #432 to the author of that change. It seems like the kind of
thing that might happen when a module is
updated, as that
>File
> "/home/jm58660/sage/local/lib/python2.7/site-packages/sagenb/flask_version/worksheet.py",
>
>
> line 879, in worksheet_publish
> print worksheet_publish.url_for(worksheet)
>
>File
> "/home/jm58660/sage/local/lib/python2.7/site-packages/sagenb/flask_version/worksheet.py"
Kcrisman said to check logs. Here they are:
Traceback (most recent call last):
File
"/home/jm58660/sage/local/lib/python2.7/site-packages/flask/app.py", line
1475, in full_dispatch_request
rv = self.dispatch_request()
File
"/home/jm58660/sage/local/lib/python2.7/site-packages/flask/
On Fri, 25 Aug 2017, kcrisman wrote:
But see that
https://github.com/sagemath/sagenb/commit/7bff646746bfad908a431621eedeb55296594d85
fixes something similar
to this, I am guessing, based on https://stackoverflow.com/a/25496041/782821
In
fact, https://github.com/sagemath/sagenb/issues/420 se
On Friday, August 25, 2017 at 5:54:00 AM UTC-4, Dima Pasechnik wrote:
>
>
>
> On Friday, August 25, 2017 at 6:42:54 AM UTC+1, Jori Mäntysalo wrote:
>>
>> On Thu, 24 Aug 2017, kcrisman wrote:
>>
>> > OK. What packages or parts have been updated lately?
>> >
>> >
>> > See perhaps https://
On Friday, August 25, 2017 at 6:42:54 AM UTC+1, Jori Mäntysalo wrote:
>
> 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
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 #23066
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 y
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 followin
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. What
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
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
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 th
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
https://stackoverflo
On Tue, 22 Aug 2017, kcrisman wrote:
What happens if you ignore that and directly do sage --notebook=sagenb?
Tested, no help. The same internal error, but the publishing and
unpublishing works.
--
Jori Mäntysalo
On Tue, 22 Aug 2017, kcrisman wrote:
You'll note these are all errors about the custom notebook conversion app that
is now the default, not sagenb per se.
I wonder whether that app is interfering somehow with the normal running of
sagenb. What happens if you ignore that
and directly do sage
On Monday, August 21, 2017 at 1:43:54 AM UTC-4, Jori Mäntysalo wrote:
>
> On Fri, 18 Aug 2017, kcrisman wrote:
>
> > BuildError: Could not build url for endpoint 'worksheet_publish'
> with
> > values ['id', 'username']. Did you mean
> 'worksheet.worksheet_publish'
> > inste
On Fri, 18 Aug 2017, kcrisman wrote:
BuildError: Could not build url for endpoint 'worksheet_publish' with
values ['id', 'username']. Did you mean 'worksheet.worksheet_publish'
instead?
Hmm. Probably related:
https://ask.sagemath.org/question/38486/build-error-when-uploading
On Wednesday, August 16, 2017 at 1:07:34 PM UTC-4, Jori Mäntysalo wrote:
>
> Strange little error: both publishing and stopping to publish give "500:
> Internal server error." Publishing works, it's just little oddity. Logfile
> has this line:
>
> BuildError: Could not build url for endpoint '
20 matches
Mail list logo
