It might be helpful to know where in GraphPlot the layout engine is chosen,
and which one corresponds to which picture. I think I understand that it
depends on GraphPlot._arcs and GraphPlot._arcdigraph. However, I cannot
find out why the first graph D gets pinkish vertices, and the second
>
> Coincidentally, I just discovered this feature myself in the process
> of preparing a little patch to the patchbot. This could be really
> sluggish for the Windows patchbot, so I'll probably just disable it in
> the settings.
The feature (allowing to test unsafe tickets) seems broken
On 2017-06-26 13:26, Erik Bray wrote:
> I submitted a PR [1] to the sage patchbot to add a feature I would
> like to have, that re-runs failed tests one or more times. If
> previously failing tests pass on a repeat attempt then the test is
> considered "passing". However, I added a new return
Hi patchbot-interested folks,
I submitted a PR [1] to the sage patchbot to add a feature I would
like to have, that re-runs failed tests one or more times. If
previously failing tests pass on a repeat attempt then the test is
considered "passing". However, I added a new return status called
On Mon, Jun 26, 2017 at 6:03 PM, Kwankyu Lee wrote:
> Hi,
>
> If a patch to a ticket put files in src/ext, then the ticket is considered
> "unsafe", and the patchbot treat it with caution. In particular, the
> patchbot clones sage into /tmp and builds it with the patch there.
Hi,
If a patch to a ticket put files in src/ext, then the ticket is considered
"unsafe", and the patchbot treat it with caution. In particular, the
patchbot clones sage into /tmp and builds it with the patch there. This
causes the building time (and the size of the log file) increase
I am not sure whether this is a bug, in any case I'd need a workaround.
Consider (with dot2tex installed)
D = DiGraph([(0, 1, 0), (1, 2, 0), (2, 3, 0), (2, 4, 0)], multiedges=True);
D.plot(layout="acyclic")
E = DiGraph([(0, 1, 0), (1, 2, 0), (2, 3, 0), (2, 4, 0), (2, 4, 1)],
multiedges=True);