Pylint: Pyreverse: working without without init.py files

Created on 22 Feb 2019 · 4Comments · Source: PyCQA/pylint

This ability already requested in https://github.com/PyCQA/pylint/issues/842, But I think it's only for Pylint, not Pyreverse.

With PEP 420 -- Implicit Namespace Packages I can work seamlessly without ever needed the __init__.py files. But when it comes to generating class diagram with Pyreverse, I have to add them unless it didn't work

My current dirty-solution is to add __init__.py to all my project folder temporarily, then stash them back and forth. Indeed it's not convenience experience.

Hope Pyreverse will work without __init__.py

Step to reproduce

With this directory structure

Myproject.py
├── Controllers
├── Model
├── Resources
│   ├── img
│   └── ui
└── Views

and $ pyreverse -my -A -o png -p myprojectname .

Thank you for Pyreverse.

enhancement topic-pyreverse

Source

azzamsa

Most helpful comment

Is anyone still looking into this? Haven't spend much time on it yet but explicit namespacing seems to be enforced in the function defined here

https://github.com/PyCQA/pylint/blob/30b2ae713eb4453b305407772b29ea68d7c3d074/pylint/pyreverse/inspector.py#L332

More specifically in line:

https://github.com/PyCQA/pylint/blob/30b2ae713eb4453b305407772b29ea68d7c3d074/pylint/pyreverse/inspector.py#L354

Do you agree? I might be interested to pick up this issue

ThomasHagebols on 13 Mar 2020

👍3

All 4 comments

Sounds like a good suggestion, thanks for reporting it!

PCManticore on 22 Feb 2019

👍1

We give a lot of hope to Pyreverse. Hope I can contribute back.

I don't know why in such tremendous amount of library in Python ecosystem, where choosing between them is so confusing. We have one and the only UML generating library that works. Other lib last release is years years ago.

azzamsa on 23 Feb 2019

Thanks for the kind words @azzamsa If you want to open a PR, I'd be happy to review or offer suggestions.

PCManticore on 27 Feb 2019