You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a project I'm working on, I use pydot to handle directed graphs as trees, and it is vital for me that the order of "children" of a node (speaking in the language of trees) is respected. I know that for dot, and therefore pydot, there's no such a thing as a tree as I mean it. Therefore the order of "children" of a node depends on how edges are internally represented by pydot.
Does this library make any guarantees on the order of its nodes? I'm building some programmatically, as pictured below
and so far, the nodes order reflected the order of insertion, which is what I expected and wanted. However, there's no statement in the documentation nor elsewhere that assures this is always the case. As far as I know, it could just depend by my own setup.
The text was updated successfully, but these errors were encountered:
For a project I'm working on, I use
pydot
to handle directed graphs as trees, and it is vital for me that the order of "children" of a node (speaking in the language of trees) is respected. I know that for dot, and thereforepydot
, there's no such a thing as a tree as I mean it. Therefore the order of "children" of a node depends on how edges are internally represented bypydot
.Does this library make any guarantees on the order of its nodes? I'm building some programmatically, as pictured below
and so far, the nodes order reflected the order of insertion, which is what I expected and wanted. However, there's no statement in the documentation nor elsewhere that assures this is always the case. As far as I know, it could just depend by my own setup.
The text was updated successfully, but these errors were encountered: