Draw module internal dependencies

Hi,

my question somewhat relates to issue #25.

First, I encounter the same issue as outlined in that ticket. It got closed without addressing the issue unfortunately. The workaround mentioned there correctly works in the way that the python files become part of the output.

But the workaround does not work in case a modules file imports another file from the same module.

Given

mydir
|   `-- __init__.py
|   `-- controller.py
|   `-- database.py
|   `-- exceptions.py
|   `-- mainclass.py
    `-- models.py

and mydir.controller imports and uses mydir.database, then this dependency is not available in the graph.

Is there any way to make this dependency visible? I would like to use that information as it would ease refactoring / organizing code as it would greatly make internal oddities visible.

Kind regards alex

[afischer-opentext-com]

Ah, thanks for the quick reply! You understood me fully correctly. I see that this works with relative imports. The project I was testing with, uses absolute imports, even for files in the same module. I see if I can change that. Still, those absolute imports are not visible.

[thebjorn]

Hi @intiamaru and thanks for your interest in pydeps. Since I can’t reproduce this problem, it would be helpful with a complete description of how to reproduce it…