-
-
Notifications
You must be signed in to change notification settings - Fork 584
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
Add configuration to ensure a newline before each comment #1000
Add configuration to ensure a newline before each comment #1000
Conversation
This adds a `ensure_newline_before_comments` configuration that matches the format that `black` imposes (for better or worse) and allows `isort` to be used with `black` without any thrashing/conflicts with regards to blank lines before comments. Should help address psf/black#251
Codecov Report
@@ Coverage Diff @@
## develop #1000 +/- ##
===========================================
- Coverage 89.77% 89.75% -0.03%
===========================================
Files 12 12
Lines 2680 2693 +13
Branches 457 461 +4
===========================================
+ Hits 2406 2417 +11
- Misses 186 187 +1
- Partials 88 89 +1 |
this implementation would be very helpful. |
Remove blank lines per black
Fix method redefinition due to bad merge
@FuegoFro This is great! Thanks for working on this! |
Thank you for the merge! 😀 |
waiting for PyCQA/isort#1000 Author: Ivan Ogasawara <ivan.ogasawara@gmail.com> Closes #1963 from xmnlab/black-files-formatting and squashes the following commits: 9d1defb [Ivan Ogasawara] Re-formatting all files using pre-commit hook
Confirmed current master fixes the problem. Is there a schedule for the next release? It would help unblock formatting pip with Black+isort. Thanks! |
@hugovk I can get it scheduled comfortably for 2 weeks for now. if it is really urgent I can try to get the release in good shape within a week. I hate to block the work on pip! Let me know, Thanks! ~Timothy |
Thanks! I don't know how long it'll take for the PR to be reviewed (it's big!) so let's ask over there: pypa/pip#7084. |
Hi hi. Don't worry about that -- We can easily wait for the next release of isort for doing this, so please feel free to make the release at a time that's comfortable for you. No pressure from our end. :) AFAIK, we're in no hurry to adopt black (we already use isort!) even though I don't think anyone is opposed to it at this point. 🙃 Thanks for all of your (and other contributors') work on isort! |
waiting for PyCQA/isort#1000 Author: Ivan Ogasawara <ivan.ogasawara@gmail.com> Closes ibis-project#1963 from xmnlab/black-files-formatting and squashes the following commits: 9d1defb [Ivan Ogasawara] Re-formatting all files using pre-commit hook
Hey! Just wondering if there was any news on a release that has this change in it. No rush! Just curious 🙂 |
Hi @FuegoFro, I've finished the other project that I wanted to finish up before the release: https://timothycrosley.com/project-7-streamdeck_ui and switched to spending all my OpenSource time working on preparing the isort 5.0.0 release. I hope to have it wrapped up soon. Thanks! ~Timothy |
Hey there! Just checking in again to see if any progress has been made on a new release 🙂 |
Since PyCQA#1000 was merged to address black compatibility, best include it in the profile.
@timothycrosley Gentle nudge on 5.0.0. :) Are there any release blocker issues that we could help you with? |
Yes, please make a new release as we cannot use unreleased code in production. |
Any news on this? Thanks! |
Can we help with the release somehow? |
This comment has been minimized.
This comment has been minimized.
Needs a new release for PyCQA/isort#1000 to be available.
Needs a new release for PyCQA/isort#1000 to be available.
@timothycrosley would it be possible to push a 4.3.x release with this feature added ahead of the move to 5.0.0? This is currently blocking projects from using isort where we would love to be able to make use of isort and black together. |
Comments in import blocks cause disagreement between Black and isort. This will soon be fixed by specifying 'ensure_newline_before_comments=true' in the isort config, though this won't be honoured until the next isort release. See psf/black#251 and PyCQA/isort#1000
Comments in import blocks cause disagreement between Black and isort. This will soon be fixed by specifying 'ensure_newline_before_comments=true' in the isort config, though this won't be honoured until the next isort release. See psf/black#251 and PyCQA/isort#1000
Comments in import blocks cause disagreement between Black and isort. This will soon be fixed by specifying 'ensure_newline_before_comments=true' in the isort config, though this won't be honoured until the next isort release. See psf/black#251 and PyCQA/isort#1000
Comments in import blocks cause disagreement between Black and isort. This will soon be fixed by specifying 'ensure_newline_before_comments=true' in the isort config, though this won't be honoured until the next isort release. See psf/black#251 and PyCQA/isort#1000
Comments in import blocks cause disagreement between Black and isort. This will soon be fixed by specifying 'ensure_newline_before_comments=true' in the isort config, though this won't be honoured until the next isort release. See psf/black#251 and PyCQA/isort#1000
Looks like 5.0.0 is releasing tomorrow: 2ea917e |
This adds a
ensure_newline_before_comments
configuration that matches the format thatblack
imposes (for better or worse) and allowsisort
to be used withblack
without any thrashing/conflicts with regards to blank lines before comments.Should help address psf/black#251