-
Notifications
You must be signed in to change notification settings - Fork 174
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
[BUG] --no-style-warnings option stopped working in 1.7.0 #488
Comments
@f11r you're probably right - can you post your configuration? Either the prospector profile or the command line arguments you are using? |
Here's our command line call: As configuration we only have a |
@f11r As a workaround, I think if you create a
This should get you the old behaviour with I'll look into what happened but I think trying to be backwards compatible added an edge case. I'll create a bugfix release when I have one! |
Fixed on master branch, will go out in a 1.7.1 release soon(ish) |
@carlio Great to see this getting fixed so quickly 🙌 |
It looks like the
--no-style-warnings
option stopped working in the newest release. It's still working in 1.6.0 but after upgrading to 1.7.0 we're now getting pycodestyle errors. It's probably related to the renaming frompep8
topycodestyle
?The text was updated successfully, but these errors were encountered: