-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Split the TRAILING_COMMA feature #763
Conversation
Pull Request Test Coverage Report for Build 979
💛 - Coveralls |
We no longer add the trailing comma in 3.5.
Hey all, do you know when can we expect to have this PR merged and released? Issue #759 is currently blocking us from migrating to Black, as our project supports multiple Python version including Python 3.5. Thanks! |
@JelleZijlstra @zsol Thanks for taking care of this PR! Do you know when can we expect a new release? |
@maarcingebala sometime in April we're going to make the first stable release. |
Thanks for the info! |
Until this black PR (psf/black#763) is released the formatting adds spurious trailing commas on Python 3.5 which creates a syntax error.
Until this black PR (psf/black#763) is released the formatting adds spurious trailing commas on Python 3.5 which creates a syntax error.
Until this black PR (psf/black#763) is released the formatting adds spurious trailing commas on Python 3.5 which creates a syntax error.
Until this black PR (psf/black#763) is released the formatting adds spurious trailing commas on Python 3.5 which creates a syntax error.
Any updates on the stable release? This bug blocks our team for migrating to Black too. |
- The issue that prevented black from being used on this block was resolved in psf/black#763
Until this black PR (psf/black#763) is released the formatting adds spurious trailing commas on Python 3.5 which creates a syntax error.
It turns out that
f(*x,)
became legal in 3.5, butdef f(*x,):
only became legal in 3.6. Therefore, use two separate Features.Fixes #759.