Here's a hackish solution I got by digging into the graph_plot sourcecode:
http://git.sagemath.org/sage.git/tree/src/sage/graphs/graph_plot.py
The relevant lines are 424 - 426.
I created a GraphPlot object and modified the labels there instead of in
the original graph.
G=DiGraph({0:[1,2]})
On Tue, 9 Dec 2014, Liang Ze Wong wrote:
Here's a hackish solution I got by digging into the graph_plot
sourcecode:
http://git.sagemath.org/sage.git/tree/src/sage/graphs/graph_plot.pyThe relevant
lines are 424 - 426.
+1 for remembering this. I hope that someone who knows graphcis can check
Yes we do, but not as completely as x86. For instance the last version that
has an arm binary in the download page is 5.13.
The Wolfram language, which is something like a strpped version of
Mathematica, is included in the raspbian distribution. So, would raspberry
pi support fit into the
On Tue, Dec 9, 2014 at 9:20 AM, mmarco mma...@unizar.es wrote:
Yes we do, but not as completely as x86. For instance the last version that
has an arm binary in the download page is 5.13.
The Wolfram language, which is something like a strpped version of
Mathematica, is included in the
Do we have anything about that in our dev guide?
Or at least a pointer to the rest/sphinx doc? e.g.
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html
Every time I have to add doc I wonder whether I should use one or two
backticks and so on and cannot find anything in our docs...
On Tuesday, December 9, 2014 6:25:56 PM UTC+1, William wrote:
On Tue, Dec 9, 2014 at 9:20 AM, mmarco mma...@unizar.es javascript:
wrote:
Yes we do, but not as completely as x86. For instance the last version
that
has an arm binary in the download page is 5.13.
The Wolfram
I don't think we do. It would be a good idea to add a link to
http://sphinx-doc.org/rest.html, for example.
John
On Tuesday, December 9, 2014 9:26:51 AM UTC-8, Jean-Pierre Flori wrote:
Do we have anything about that in our dev guide?
Or at least a pointer to the rest/sphinx doc? e.g.
Hi!
Concerning the support problematic for ARM, Windows etc:
We should ask ourselfs if we need a more minimal Sage distribution, which
is easily portable to
ALL Platforms. The main problem with Sage on many platforms is, that some
packages often fail to build.
Especially C based packages as
On Tue, Dec 9, 2014 at 12:14 PM, maldun dom...@gmx.net wrote:
Hi!
Concerning the support problematic for ARM, Windows etc:
We should ask ourselfs if we need a more minimal Sage distribution, which is
easily portable to
ALL Platforms. The main problem with Sage on many platforms is, that
On Fri, 5 Dec 2014, Jan Groenewald wrote:
Please test the fix and report back here:
sagenb-0.11.1-py2.7.egg/sagenb/notebook/run_notebook.py:
ssl_context = SSL.Context(SSL.SSLv23_METHOD)
to
ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLSv1)
This does not make any
I don't know.
Is it harder to support a full Sage on a variety of different platforms
which are needed,
or to make a reduced Sage, where testing of the sub-distribution can be
fully contained,
in the main framework?
Additionally to that, we have to keep in mind that while sage grows in
In
http://www.sagemath.org/doc/reference/structure/sage/structure/element.html#how-to-define-a-new-element-class
,
I find the descriptions of _add_ very confusing, because it seems to imply that
there are two versions of _add_, one of them as a def and the other as a
cpdef. As it stands, it
12 matches
Mail list logo
