We could just sort vertices/edges in graphviz_string. In the cases where that is a performance problem its unlikely that you can compile the graphviz code anyways.
On Tuesday, September 29, 2015 at 4:13:08 PM UTC+2, Jeroen Demeyer wrote: > > Dear graphviz enthousiasts, > > The file src/sage/graphs/generic_graph.py has a function > graphviz_string() with many doctests. However, these doctests are bad > because they depend on implementation details, in particular the order > of keys in a dict. This causes serious doctest failures on #19304, where > the hash function for Rational is changed. > > Since the output is even different on 32-bit and 64-bit systems and the > tests are very long, the only solution I see is to add "# random" to > most of the graphviz_string() tests. But I'm open for suggestions... > > > Jeroen. > -- 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.
