On Wed, Dec 6, 2017 at 7:09 PM, David Cousens wrote:
> Hi
>
> Has anyone considered making the menu section of the sage Web interface non
> scrolling and only making the worksheet cell part of the interface
> scrollable.
What is " the sage Web interface"?
> I find
Hi
Has anyone considered making the menu section of the sage Web interface non
scrolling and only making the worksheet cell part of the interface
scrollable.
I find myself often scrolling back through a large page to reach the menu
and then having to scroll back to where I was in the
>
> Users should be able to run the EXAMPLES and see what we say they'll see.
>
+1
--
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
On 12/06/2017 09:49 AM, Erik Bray wrote:
>
> Did anyone ever think up a better solution to this?
>
Whatever you do, you wind up with a big pile of dict output in the
middle of your test case. So (where possible) you might as well use that
space to define a new dict containing the expected
I strongly dislike the idea making the doctesting framework more
complicated by parsing the output like this. I think this should only be
done as a last resort, since it makes the doctesting framework itself more
error prone, and if implemented incorrectly might even silently let real
error
On Wed, Dec 6, 2017 at 3:59 PM, Jeroen Demeyer wrote:
> On 2017-12-06 15:49, Erik Bray wrote:
>>
>> I think this question has come up before, but I don't know that
>> there's been a really satisfactory solution.
>>
>> Many of the doctests have dicts as their output (or
On 2017-12-06 15:49, Erik Bray wrote:
I think this question has come up before, but I don't know that
there's been a really satisfactory solution.
Many of the doctests have dicts as their output (or worse, contained
embedded in their output). This can fail from time to time since dict
element
I think this question has come up before, but I don't know that
there's been a really satisfactory solution.
Many of the doctests have dicts as their output (or worse, contained
embedded in their output). This can fail from time to time since dict
element order is not guaranteed. This has been
Dear all,
Thank you very much for your answers.
I can now understand that I was building incrementally, but I do not
understand what was the issue.
Finally, after many attempts, what was successful was:
>sudo make distclean
and then
>make build
I am not sure why the sudo was necessary, but
Now I believe that we have a full fix for
this: https://trac.sagemath.org/ticket/24015
(so you could install it and use it now, at your own risk :-))
some C language routines had to be fixed:
https://github.com/miguelmarco/libhomfly/pull/8
https://github.com/miguelmarco/libhomfly/pull/11
On
10 matches
Mail list logo