This is a redux #977 because I had some craziness going on in my paths.
The current release of black is 19.3b0 and it has a number of issues that affect 2.x code. These include:
- https://github.com/psf/black/issues/768:
Cannot parse: 3:19: print('hello', file=sys.stdout) - https://github.com/psf/black/issues/752: ugly whitespace
print (something)
Both issues are pretty terrible for code trying to be 2.x/3.x compatible, and both issues have been fixed in master. However, neither are part of a current release.
Can we get a new release out? If not, could we at least get a bugfix release out (19.3b1) that includes those two fixes?
chebee7i
All 15 comments
Is there anything holding this up? Or is it just that this project seems to have flatlined?
chebee7i
on 17 Sep 2019
There are plenty of commits each month so the project is still active. It would be nice to see a new beta release though.
Two workarounds until that happens:
- Use pre-commit which will let you specify a branch/tag/commit
- pip install git+https://github.com/psf/black.git@master
chingc
on 20 Sep 2019
Yeah, I've seen the commits...I question the priority though, as it seems like getting out a bug fix for a critical regression should be higher priority.
The minimal response on this and similar issues is, in part, a reason why one might question the overall status of the project.
Bottom line for me is that this release is broken, and the fix is really quite simple given that the commits are already integrated in master. Workarounds are fine but no replacement for fixing the release.
chebee7i
on 23 Sep 2019
I agree that it makes sense to get another (pre)release out ASAP, without waiting for other in-flight changes. @ambv @zsol what do you think?
JelleZijlstra
on 30 Sep 2019
+1 to a new beta (or better).
This (and isort, but there'll be a new isort release soon) is also blocking using Black on pip: https://github.com/pypa/pip/pull/7084#issuecomment-535839539.
hugovk
on 30 Sep 2019
I'm all in favor for more frequent releases in general so: yes 馃槑
zsol
on 30 Sep 2019
OK, let's do a new beta on Thursday. Let's flag what we can finish and merge until then.
ambv
on 30 Sep 2019
I just tested out current master on our codebase and unfortunately I found two new issues: #1041 and (more serious) #1042. I may have some time later to try to fix them.
JelleZijlstra
on 3 Oct 2019
Also https://github.com/psf/black/issues/1044 from running master on pip. Possibly duplicates of those two.
hugovk
on 3 Oct 2019
It does not seem like black was released on 2 weeks ago. Is a new release of black dependent on resolving:
- #1041
- #1042
- #1044
quasiben
on 14 Oct 2019
yes
zsol
on 14 Oct 2019
Black 19.10b0 has just been released, can this be closed?
hugovk
on 29 Oct 2019
I hope so. @chebee7i, can you confirm the new release fixed things for you?
ambv
on 29 Oct 2019
Latest version 19.10b0 fixes #752.
jd
on 15 Nov 2019
Has this been switched to the stable branch? I am (per the vim instructions) using the latest stable version of black and I still hit this issue. I commented here: https://github.com/psf/black/issues/988
It seems like the commit should be there: https://github.com/psf/black/commit/d6db1c12a8e14833fe22da377cddc2bd1f43dc14
However I am hitting this issue today (june 2020) with the latest stable black while editing python 2.7 code using let g:black_target_version=27 in vimrc
tommyjcarpenter
on 19 Jun 2020
Related issues
Kristinita
路
28Comments
adamehirsch
路
48Comments
kindjacket
路
21Comments
altendky
路
41Comments
Lukas0907
路
66Comments
Most helpful comment
OK, let's do a new beta on Thursday. Let's flag what we can finish and merge until then.