CircularDependencyError should return the graph nodes/edges as Python objects along with the error message

[Former user]

Hi,

Yesterday I had to debug a circular dependency error, and having to make sense of a cca. 150 KByte long error message was not an easy task. Had the CircularDependencyError object contained the real graph nodes/edges and not just their repr(), I could have used e.g. python-graph to visualize the data, which would have made spotting the error much more easier.

Gabor

[Mike Bayer]

are you on 0.6 at least ? the topological structure has been dramatically simplified. e.g.:

CircularDependencyError: Circular dependency detected: cycles: set('node3', 'node2', 'node5', 'node4', ('node4', 'node1'), ('node2', 'node3'), ('node1', 'node2'), ('node4', 'node5'), ('node5', 'node4')](('node3',)

but sure we could stick those two members onto the exception.

[Mike Bayer]

that also helped with the tests, thanks for the suggestion. e9e221977bde7724d4ef3b553de4f982028eead8

[Mike Bayer]

removed itertools in a9875e395025c28c728ed4afb50036a81a07b0a2

[Mike Bayer]

Removing milestone: 0.6.5 (automated comment)