-
-
Notifications
You must be signed in to change notification settings - Fork 276
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 regression after #857 (astroid 2.5) #930
Comments
Some notes:
One workaround fix, that feels like a hack until I understand the problem better, is for I have written some new unit tests for this issue and extended the existing ones, but there is some fundamental logic underpinning the use of My unit tests look at both virtual and ondisk paths (because of the .. and I thought this fix was going to be easy. |
See astroid #930 for more details pylint-dev/astroid#930
@doublethefish thanks for your report and investigation. |
It seems like this happens if an import inside a package which is at least two levels deep is processed. |
This is further fix for sphinx-pyreverse#25 now that the upstream has been fixed See astroid pylint-dev/astroid#930
This is further fix for sphinx-pyreverse#25 now that the upstream has been fixed See astroid pylint-dev/astroid#930
Steps to reproduce
<pylint checkout>
source .tox/py39/bin/activate
or similar (you may need to run a tox session first)astroid
ac2b173 or laterastroid
(python3 -m pip install -e <path-to-astroid>
) as dependencies may be differentpyreverse --output png --project test tests/data
Current behaviour
A
ModuleNotFoundError
exception is raised.Expected behaviour
No exception should be raised. Prior to #857 no exception was raised.
python -c "from astroid import __pkginfo__; print(__pkginfo__.version)"
output2.6.0-dev0
(cab9b08)The text was updated successfully, but these errors were encountered: