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
why this style? #104
Comments
you can't |
also the bikeshed is already painted :) |
other [-]s from the proposal:
|
However, a flag to disable the conversion from Personally, I'd like to have the last one especially. In my team, people know the standard library modules and do not want them wordily listed out, wasting vertical space at the start of every file. |
I don't care about your personal style and neither does the tool, if you don't like what it does use something else you're also missing the point |
Rude. |
no you, you're commenting on a 3 year old closed issue asking to add a bunch of flags to go against the core design principles of the tool -- ones which prevent you from having merge conflicts. |
in case you missed the readme which uses almost exactly your example as rationale -- https://github.com/asottile/reorder_python_imports#why-this-style or PEP8 which discourages your second proposal https://peps.python.org/pep-0008/#imports |
Fair enough, thanks for the answer. I do appreciate the tools existence and your time, wish that would have been your first reply. |
if you're interpreting "no" as "tearing you a new one" you need to seriously reconsider your sensitivity |
Why not
?
It also doesn't conflicts and you have shorter, maybe even more readable lines.
The text was updated successfully, but these errors were encountered: