On 2014-11-06 02:41, kcrisman wrote:
>
> It is an interface that worked the same way for a long time and
> achieved
> de facto status.
>
>
> Fine, if you don't want a way to start the ipython notebook then I can
> take
> out the optional argument.
>
>
> Perhaps I wil
>
> > If anyone has a few moments and is using the notebook with this rc, I'd
> > appreciate someone confirming for me that creating new cells in the live
> > documentation no longer works.
>
> I confirm that, on rc1, clicking on the blue line above a cell does not
> create a new cell on the
> I think I’ve found the problem code (which actually hasn’t changed). In
> sagenb/data/sage/html/notebook/worksheet_page.html the following lines
> exclude the code that binds click actions to the icon divs in the case of
> the tutorial.
>
>
Yes, I found this as well.
> {% if not worksh
> It is an interface that worked the same way for a long time and achieved
>> de facto status.
>>
>
> Fine, if you don't want a way to start the ipython notebook then I can
> take out the optional argument.
>
Perhaps I will leave it to those who use this feature to comment next. I
assume t
I think I’ve found the problem code (which actually hasn’t changed). In
sagenb/data/sage/html/notebook/worksheet_page.html the following lines exclude
the code that binds click actions to the icon divs in the case of the tutorial.
{% if not worksheet.docbrowser() %}
.
.
.
{%endif%}
All I did
I’ve found the problem. Somehow in the live docs the script that binds events
to the icons and divs for making new cells is empty. We need to trace where
those are made in the docs. I’ve got a few more minutes I can spend on this.
If I find it I will post here.
Jonathan
On Nov 5, 2014, at 5
Well, I am taking suggestions on how to debug it because so far I haven't
had much success. I am probably thinking too hard about it.
Francois
On Wed, 05 Nov 2014 02:36:53 Volker Braun wrote:
> Haven't seen that one before, should be easy to debug though.
>
> On Wednesday, November 5, 2014 2:26
Hi,
On Wed, Nov 05, 2014 at 01:48:04PM -0800, kcrisman wrote:
> If anyone has a few moments and is using the notebook with this rc, I'd
> appreciate someone confirming for me that creating new cells in the live
> documentation no longer works.
I confirm that, on rc1, clicking on the blue line
If anyone has a few moments and is using the notebook with this rc, I'd
appreciate someone confirming for me that creating new cells in the live
documentation no longer works.
I'm uncertain as to whether this is a bug or a feature, though I believe
from blame and history that it was due to so
On Wednesday, November 5, 2014 9:28:38 PM UTC, kcrisman wrote:
>
> It is an interface that worked the same way for a long time and achieved
> de facto status.
>
Fine, if you don't want a way to start the ipython notebook then I can take
out the optional argument.
--
You received this message
> No. People write scripts against this, so it’s an API change.
>>
>
> No. If you screen scrap the output and run image recognition on the window
> content then its still a UI, even if you built a crappy API around it.
>
I don't really care if you call it a UI or API; this will be moot to
On Wednesday, November 5, 2014 5:13:04 PM UTC, Ivan Andrus wrote:
>
> No. People write scripts against this, so it’s an API change.
>
No. If you screen scrap the output and run image recognition on the window
content then its still a UI, even if you built a crappy API around it.
--
You rece
On Nov 5, 2014, at 9:44 AM, Volker Braun wrote:
On Wednesday, November 5, 2014 4:23:59 PM UTC, kcrisman wrote:
>
> Yeah, I kind of agree, since even though "it's not a hand-written parser"
> it still is an API change.
>
UI change, not API.
No. People write scripts against this, so it’s an API
On Wednesday, November 5, 2014 4:23:59 PM UTC, kcrisman wrote:
>
> Yeah, I kind of agree, since even though "it's not a hand-written parser"
> it still is an API change.
>
UI change, not API.
I'm against second-guessing what the input might mean. The command line UI
rules are IMHO clear and exa
> > IMHO that is the expected outcome for an optional command line argument.
> If you
> > don't want the command line parsing to end (and not treat "directory..."
> as
> > value) then you should use
> >
> > sage -n -- directory=sage.sagenb
>
> I'd appreciate if we would have a deprecation
Haven't seen that one before, should be easy to debug though.
On Wednesday, November 5, 2014 2:26:34 AM UTC, François wrote:
>
> I have these rather unpleasant failure:
> sage -t --long --warn-long 76.2 src/sage/tests/cmdline.py
> ***
16 matches
Mail list logo
