Support for namespace packages (PEP 420)

PEP 420 introduced implicit namespace packages, which are packages without __init__.py. Those packages, and the modules under them, don’t seem to appear in the dependency graph generated by pydeps.

Here’s an example. Given the following directory structure:

.
├── main.py
├── pkg1
│   └── foo.py
└── pkg2
    ├── bar.py
    └── __init__.py

And main.py:

import pkg1.foo
import pkg2.bar

pydeps main.py generates the following graph:

I would have expected pkg1.foo to be included in the dependency graph. (On the other hand, I’m not sure there’s a point in having pkg1 there since it’s going to be empty.)

[ssbarnea]

That is a huge bug and --include-missing seems to avoid it but not without nasty side effects. Sadly I will not be able to adopt pydeps as part of the docs until is fixed.

[thebjorn]

@ssbarnea I’m wondering if you’re using this feature to create namespace package, or if it’s simply to avoid having an __init__.py file? I’ve never found a reason to use namespace packages that outweigh the mess it causes. Regardless, pydeps is dependent on modulefinder (a python standard module - vendorized with some bug-fixes) supporting the feature first. I’ll happily merge a PR if you or anyone else wants to work on it though…