Re: [sage-devel] Re: Graph.show() and non-injective relabeling
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]})
Gplot = G.graphplot()
# Extract relevant components
node_list = Gplot._nodelist
pos_dict = Gplot._pos
# Define list or dict of labels (same length as node_list)
label_list = [Ho,Hi,Hi]
# Modify vertex labels
Gplot._plot_components['vertex_labels'] = [text(label, pos_dict[node],
rgbcolor=(0,0,0), zorder=8) for node,label in zip(node_list,label_list)]
Gplot.show()
You could probably condense it into a two or three liner.
It seems like it should also be possible to label vertices with non-text as
well (e.g. other graphics components).
Regards,
Ze
On Tuesday, October 14, 2014 2:50:05 AM UTC-7, Jori Mantysalo wrote:
On Tue, 14 Oct 2014, Nathann Cohen wrote:
G=DiGraph({0:[1,2]})
G.set_edge_label(0,1,'Hi!')
G.set_edge_label(0,2,'Hi!')
(But .relabel(lambda e: ...) -syntax is easier, I think.)
Yes but we can't do the same for the vertices of a graph, of we would
have no way to differentiate them afterwards. It should really be a
plot parameter.
That was what I was thinking. I don't know if relabel is good name for
parameter of plot(). Maybe not.
--
Jori Mäntysalo
--
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 to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Graph.show() and non-injective relabeling
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 if this works correctly. It seems like it should also be possible to label vertices with non-text as well (e.g. other graphics components). That would be nice. A simple example could be having LaTeX-parsed strings as labels. -- Jori Mäntysalo
Re: [sage-devel] Re: User Survey
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 mission statement? El lunes, 8 de diciembre de 2014 23:10:49 UTC+1, William escribió: On Mon, Dec 8, 2014 at 2:05 PM, Jean-Pierre Flori jpf...@gmail.com javascript: wrote: On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote: Maybe support for arm architecture would be relevant in that respect. We do support ARM, don't we? At least I'm able to compile Sage from scratch on a Raspberry Pi and on armv7+ as well. Awesome! And yes we do. Again, as this thread is titled User Survey, let's say that the survey question might be: Do you *care* about support for Sage on ARM devices such as Raspberry Pi, etc.? William -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: User Survey
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 raspbian distribution. So, would raspberry pi support fit into the mission statement? Definitely, yes it does, without any question. -- William El lunes, 8 de diciembre de 2014 23:10:49 UTC+1, William escribió: On Mon, Dec 8, 2014 at 2:05 PM, Jean-Pierre Flori jpf...@gmail.com wrote: On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote: Maybe support for arm architecture would be relevant in that respect. We do support ARM, don't we? At least I'm able to compile Sage from scratch on a Raspberry Pi and on armv7+ as well. Awesome! And yes we do. Again, as this thread is titled User Survey, let's say that the survey question might be: Do you *care* about support for Sage on ARM devices such as Raspberry Pi, etc.? William -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] rest syntax
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... -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: User Survey
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 language, which is something like a strpped version of Mathematica, is included in the raspbian distribution. So, would raspberry pi support fit into the mission statement? Definitely, yes it does, without any question. -- William So we need a raspberry pi buildbot... Who can afford it? :) (At least as long as we cannot properly cross-compile sage, which will surely not happen in the near future... though sage-on-gentoo and lmonade exist.) -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: rest syntax
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. 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... -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: User Survey
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 troublemakers. I absolutely don't want to close out these packages! But we should consider a subset of Sage (let's call it MiniSage) which is easier portable and more slender, but which contains enough functionality for the average user. This gives the developers more time to polish out problems with packages of the traditional Sage, while maintaining and improving functionality of the core set on the device in question. That would come to the following new structure: Minimal Packages (MiniSage)- Core Packages (traditional Sage) - optional Packages ... -Stefan 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 language, which is something like a strpped version of Mathematica, is included in the raspbian distribution. So, would raspberry pi support fit into the mission statement? Definitely, yes it does, without any question. -- William El lunes, 8 de diciembre de 2014 23:10:49 UTC+1, William escribió: On Mon, Dec 8, 2014 at 2:05 PM, Jean-Pierre Flori jpf...@gmail.com wrote: On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote: Maybe support for arm architecture would be relevant in that respect. We do support ARM, don't we? At least I'm able to compile Sage from scratch on a Raspberry Pi and on armv7+ as well. Awesome! And yes we do. Again, as this thread is titled User Survey, let's say that the survey question might be: Do you *care* about support for Sage on ARM devices such as Raspberry Pi, etc.? William -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: User Survey
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 some packages often fail to build. Especially C based packages as troublemakers. I absolutely don't want to close out these packages! But we should consider a subset of Sage (let's call it MiniSage) which is easier portable and more slender, but which contains enough functionality for the average user. This gives the developers more time to polish out problems with packages of the traditional Sage, while maintaining and improving functionality of the core set on the device in question. That would come to the following new structure: Minimal Packages (MiniSage)- Core Packages (traditional Sage) - optional Packages ... I think everybody would want to have such a thing. In practice, it is a simply a lot of work (especially for the release manager), and we have very limited resources in that regards, to put it mildly... If we had more resources, there are so many things like this that I would want us to do. -Stefan 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 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 raspbian distribution. So, would raspberry pi support fit into the mission statement? Definitely, yes it does, without any question. -- William El lunes, 8 de diciembre de 2014 23:10:49 UTC+1, William escribió: On Mon, Dec 8, 2014 at 2:05 PM, Jean-Pierre Flori jpf...@gmail.com wrote: On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote: Maybe support for arm architecture would be relevant in that respect. We do support ARM, don't we? At least I'm able to compile Sage from scratch on a Raspberry Pi and on armv7+ as well. Awesome! And yes we do. Again, as this thread is titled User Survey, let's say that the survey question might be: Do you *care* about support for Sage on ARM devices such as Raspberry Pi, etc.? William -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] About SSLv3 security hole
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 difference. The command curl -v3 -X HEAD https://my.server.here opens connection. -- Jori Mäntysalo
Re: [sage-devel] Re: User Survey
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 functionality, more modularity gives better maintainability, which could be necessary someday anyway, And the main question: Does this really concern that much packages? If the number would be countable on one hand, it should really be considerd. On Tuesday, December 9, 2014 9:42:05 PM UTC+1, William wrote: On Tue, Dec 9, 2014 at 12:14 PM, maldun dom...@gmx.net javascript: 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 some packages often fail to build. Especially C based packages as troublemakers. I absolutely don't want to close out these packages! But we should consider a subset of Sage (let's call it MiniSage) which is easier portable and more slender, but which contains enough functionality for the average user. This gives the developers more time to polish out problems with packages of the traditional Sage, while maintaining and improving functionality of the core set on the device in question. That would come to the following new structure: Minimal Packages (MiniSage)- Core Packages (traditional Sage) - optional Packages ... I think everybody would want to have such a thing. In practice, it is a simply a lot of work (especially for the release manager), and we have very limited resources in that regards, to put it mildly... If we had more resources, there are so many things like this that I would want us to do. -Stefan 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 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 raspbian distribution. So, would raspberry pi support fit into the mission statement? Definitely, yes it does, without any question. -- William El lunes, 8 de diciembre de 2014 23:10:49 UTC+1, William escribió: On Mon, Dec 8, 2014 at 2:05 PM, Jean-Pierre Flori jpf...@gmail.com wrote: On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote: Maybe support for arm architecture would be relevant in that respect. We do support ARM, don't we? At least I'm able to compile Sage from scratch on a Raspberry Pi and on armv7+ as well. Awesome! And yes we do. Again, as this thread is titled User Survey, let's say that the survey question might be: Do you *care* about support for Sage on ARM devices such as Raspberry Pi, etc.? William -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from
[sage-devel] Confusing documentation in element.pyx
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 reads like a circular argument. def RingElement._add_: ... You should override _add_. The default implementation of this function is to call _add_ . cpdef RingElement._add_ ... which will happen if no-one has supplied implementations of either _add_ I think that it does not help that Pyrex is still mentioned instead of Cython. I opened ticket #17480 and, as a starter, pushed a branch correcting several ReST formatting issues. For the above descriptions, I do need help by someone who knows what is meant. Thanks, CH -- 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 to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
