-
Notifications
You must be signed in to change notification settings - Fork 117
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
duplicate-except throws red-herring on DoesNotExist #81
Comments
I can reproduce this too. |
atodorov
added a commit
that referenced
this issue
Jan 18, 2018
atodorov
added a commit
that referenced
this issue
Jan 19, 2018
Hey guys, cannot test yet on my full app because of a bug in pylint that prevents us from moving above 1.7.x But thanks for the fix. I'll let you know if I experience further issues Cheers |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys, I have the following issue.
I raised it originally to the pylint team who thinks this is actually due to some processing you are doing with the DoesNotExist (I guess for other code checks)!
pylint-dev/pylint#1050
Steps to reproduce
Current behavior
This raises a W0705 duplicate-except saying it's catching django.core.exceptions.ObjectDoesNotExist. both those exception (as far as I understand it) are indeed inheriting from ObjectDoesNotExist (common ancestor), but they are not the same class
Expected behavior
Do not raise this issue on common ancestor
pylint --version output
pylint 1.5.6,
astroid 1.4.6
Python 2.7.12 (default, Jun 29 2016, 14:05:02)
[GCC 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31)]
The text was updated successfully, but these errors were encountered: