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 pablogsal
Recipients belopolsky, christian.heimes, eric.smith, gdr@garethrees.org, martin.panter, pablogsal, remi.lapeyre, rhettinger, terry.reedy, tshepang
Date 2019-01-20.21:34:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1548020043.01.0.853766669534.issue17005@roundup.psfhosted.org>
In-reply-to
Content
Although I think the API with the dictionary may be cleaner, I still do not like it completely.

1) One of the reasons is that implementing C3 directly with the topological sort is not straightforward as the different nodes that are at the same level are unordered and therefore any permutation of all these is a valid topological sort, while C3 comes from a stable sort. The version with pairs is stable on the other hand.

2) Topological sorting usually is well-defined on totally connected graphs, so I do not know what exactly it means to topologically sort two disjoint graphs. This was one of the main drawbacks of the tuple-based approach, but I think it may be a good property.
History
Date User Action Args
2019-01-20 21:34:05pablogsalsetrecipients: + pablogsal, rhettinger, terry.reedy, belopolsky, eric.smith, christian.heimes, tshepang, gdr@garethrees.org, martin.panter, remi.lapeyre
2019-01-20 21:34:03pablogsalsetmessageid: <1548020043.01.0.853766669534.issue17005@roundup.psfhosted.org>
2019-01-20 21:34:03pablogsallinkissue17005 messages
2019-01-20 21:34:02pablogsalcreate