New Release To Fix 2.7

[chebee7i]

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:

• black fails on print function when using Python 2.7 as target version #768: Cannot parse: 3:19: print('hello', file=sys.stdout)
• black inserts unnecessary whitespace around print() with target_version = py27 #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]

Is there anything holding this up? Or is it just that this project seems to have flatlined?

[chingc]

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:

1. Use pre-commit which will let you specify a branch/tag/commit
2. pip install git+https://github.com/psf/black.git@master

[chebee7i]

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.

[JelleZijlstra]

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?

[hugovk]

+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: pypa/pip#7084 (comment).

[zsol]

I'm all in favor for more frequent releases in general so: yes 😎

[ambv]

OK, let's do a new beta on Thursday. Let's flag what we can finish and merge until then.

[JelleZijlstra]

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.

[hugovk]

Also #1044 from running master on pip. Possibly duplicates of those two.

[quasiben]

It does not seem like black was released on 2 weeks ago. Is a new release of black dependent on resolving:

• Regression: Unnecessary parens with unary minus operator #1041
• Regression: Unstable formatting on long strings #1042
• Regression with master #1044

[zsol]

yes

[hugovk]

Black 19.10b0 has just been released, can this be closed?

[ambv]

I hope so. @chebee7i, can you confirm the new release fixed things for you?

[jd]

Latest version 19.10b0 fixes #752.

[tommyjcarpenter]

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: #988

It seems like the commit should be there: d6db1c1

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