Besides, it would also be supercool to have a class Graphs analogous to the class Posets, and have the cardinality of the first few layers built in (analogous to Posets(16).cardinality()).
Martin Am Freitag, 9. März 2018 07:19:24 UTC+1 schrieb Jori Mäntysalo: > > It is much faster to say sum(1 for _ in graphs.nauty_geng(7)) than sum(1 > for _ in graphs(7)), and after #19919 we have nauty as a standard package. > > Will I break something if I change graphs(n) without any additional > parameter to use nauty? A user really needing the old code could then say > graphs(n, property=lambda x: True). I think that Sage documentation makes > no promise at all about the order in which graphs are generated. > > -- > 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
