-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Make enum.py pep8 compliant #73289
Comments
Hello, When executing flake8 on Lib/enum.py, there are lot of warning. This patch remove all these warnings. |
In general we do not accept PEP-8 patches; it is code churn with insufficient benefit since many modules in the stdlib predate either PEP-8 itself or the current version of PEP-8. However, enum is a new enough module that I suppose this might get accepted. In any case, thank you for wanting to contribute! |
I really don't like how this patch is done or even the spirit of it. To my eyes, some of the code looks worse (especially the addition of trailing backslashes and some odd line-wraps that aren't sensitive to readability or context). I'm going to close this. If Ethan wants to make minor tweaks to his whitespace or line-wrapping, I believe he can do a better job with his own code. Jean-Sebastien, thank you for trying to contribute, but PEP-8ing other people's code generally isn't helpful. I recommend that you find a tracker item that needs a patch for a substantive change and work on that. I think you will find it more satisfying and will have a much greater chance of acceptance. |
Hello Raymond Hettinger, I agree with you that PEP-8 compliant isn't useful. If you look at my patch, the first change is a unused import, not just a text formatting. Maybe this first change can be useful ? (not importing unused module) |
New changeset bf6987b93358 by Raymond Hettinger in branch '3.6': |
Thanks Raymond and Jean-Sebastien. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: