modulegraph2 is a complete rewrite of modulegraph (by the same author), using lessons learned in that project but with a complete new Python 3 code base and full test coverage.

modulegraph will no longer be maintained.

We need to identify our changes to modulegraph, identify which are relevant for modulegraph2 and port them over.

I marked this as "good first issue", since the changes are focused on a single part of the code, which has good code-coverage. I have not yet had a look at the code of modulegraph2, though, so I can not tell whether we need to change a lot.

When implementing this, you might need many cycles to get it right

• please work on a separate branch, e.g. modulegraph2
• run the test-suite locally on your system prior to pushing it anwhere
• set up your personal travis-ci and appveyor and push there first
• open the pull-request only when everything is fine and all tests pass in your travis-ci and appveyor.

This helps keeping our CI "credits" for your main development up to speed (it's slow anyway) until the code is ready. Thanks!