This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dam1784
Recipients dam1784, docs@python
Date 2021-12-14.15:20:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639495203.77.0.753963192728.issue46071@roundup.psfhosted.org>
In-reply-to
Content
The documentation for graphlib encourages users to represent their graphs in a awkward format.

Graphs are currently represented using dictionaries of nodes, for example:
graph["end_node"] = ["start_node"]

And this is unintuitive because you can't use the graph traverse edges in their forward direction.
If you look up a node in the graph, you get all of the nodes that point to the key,
as opposed to all of the nodes that the key points to.

The solution is to rewrite the documentation such that all of the edge directions are reversed.
The final topologically sorted list will be in the "opposite" direction as a consequence.

This will cause no functional changes.
History
Date User Action Args
2021-12-14 15:20:03dam1784setrecipients: + dam1784, docs@python
2021-12-14 15:20:03dam1784setmessageid: <1639495203.77.0.753963192728.issue46071@roundup.psfhosted.org>
2021-12-14 15:20:03dam1784linkissue46071 messages
2021-12-14 15:20:03dam1784create