-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Results from wrong file when files have the same name but different extensions #3631
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
Comments
Closing as this seems to have been fixed in current release:
|
Thanks for following on the issue, but I believe you wrongly closed that one. I checked locally and your example itself shows it is not fixed. The second invocation of pylint should show warnings on tests/test_deprecation.wsgi but it shows them for tests/test_deprecation.py. |
Could you provide a reproducer, please ?
|
Do you mean a pytest unit case, as a pull request? Or just a dump of command outputs? The steps to reproduce haven't changed. I am not sure what this latest command output is supposed to show. The issue happens with two files with the same extension, it works fine with just one file, so I don't understand you copying the file and then removing the first one. Your earlier post was going through the right steps and reproduces the issue. The second pylint execution should show messages for |
Ho I misunderstood the issue, my bad. |
Given two python files with the same name, one with the .py extension and another with any other extension (e.g. .wsgi), pylint always reports issues only from the file with the .py extension.
This may be working as intended (see invoking pylint with a file) but a warning of some kind would be useful.
The workaround is to not use files with the same name, regardless of the file extensions.
Steps to reproduce
Current behavior
Pylint reports issues from the file with the .py extension.
Expected behavior
Pylint reports issues from the exact file passed as argument.
OR
Pylint warns about file name collision.
pylint --version output
Python 3.8 on Windows
Python 3.7 on Linux Debian
The text was updated successfully, but these errors were encountered: