The boundary code does get used... though it's fairly specialized --
it's for the UW Math REU.
On Sun, Dec 8, 2013 at 2:58 AM, Nathann Cohen wrote:
> Hell everybody !!
>
> While working on #15278, Simon rediscovered the "boundary" graph parameter.
> Turns out that there is a line is G
On Sunday, December 8, 2013 12:15:55 PM UTC, Christian Stump wrote:
>
> import errror "No module named xmlrpc.client".
>
Sounds like you somehow managed to run it with a python2.x interpreter. Its
a python3 script.
--
You received this message because you are subscribed to the Google Groups
"s
Thanks, "sage -dev push --ticket 12345" worked like a charm, while - after
installing the git-trac module as described there - "git trac push 12345"
resulted in the import errror "No module named xmlrpc.client".
For the record, those are the sage-combinat conventions. I think they are
> quite
Hell everybody !!
While working on #15278, Simon rediscovered the "boundary" graph parameter.
Turns out that there is a line is Graph.delete_vertex (one of the things we
would like to be efficient in graphs) a line that does a linear-time
operation :
self._boundary = [v for v in self.
Hi!
I am new to the group. Could not find a way to attach log file to the post.
Hence pasting it below.
I was trying to build Sage from source on openSuse 12.2 64-bit intel i5
machine. Installation failed with the following error message. There was some
file not found for flint-2.3.pl. The instal
Its easy to script the git push + modify branch field action, for example
the sage dev scripts:
sage -dev push --ticket 12345
or using the git trac subcommand extension that I'm writing
at https://github.com/sagemath/git-trac-command:
git trac push 12345
Trac will send a notification email a
Many places in Sage have
try:
sig_on()
...
finally:
sig_off()
which is wrong (if sig_on() throws an exception, there should be no
sig_off()). This should be replaced by
sig_on()
try:
...
finally:
sig_off()
Most of these are in sage/libs/ppl.pyx and in sage/symbolic/expres
