-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyreverse
does not show inheritance relation when using a flat folder
#7686
Comments
Are there any updates on this issue? |
No one worked on it yet, do you want to contribute @nhadziosma1 ? :) |
Same issue here now. Are there any solutions? I can look try to contribute, but I'm not a pro though. |
Hey @atomic-light sure we can answer your question if you have some. Imo the first step is to add the test for that. Also do not hesitate to open a draft merge request early it's easier to talk about the issue when seeing the code directly. |
The way I would go at this would probably be:
|
…heritance link for a flat folder as described in pylint-dev#7686
Bug description
See this SO question.
Foo.py
,Bar.py
and__init__.py
are all located in the same folder.Foo.py
:Bar.py
:pyreverse
is executed from within the same folder.Configuration
No response
Command used
pyreverse -ASmy -o png .
Pylint output
Expected behavior
It could be argued that when using an
__init__.py
and therefore a package relative or absolute imports should be used, the code provided does run fine when just running e.g.python -c "import Bar"
from inside the directory.Therefore
pyreverse
should pick up the relationships between the two classes as well.Pylint version
OS / Environment
No response
Additional dependencies
No response
The text was updated successfully, but these errors were encountered: