Non-prerelease black release

[lig]

It looks like Black is stable enough at the moment to release it as stable to PyPI. There are plenty of tools and integrations already which rely on black package and the fact that it is still in prerelease state sometime causes inconveniences, i.e. using it with pipenv forces allow_prereleases flag to be set to true.

[ambv]

This will happen soon, you're right. We'll be releasing one last (planned) beta, and then an RC of a stable release.

[gforcada]

@ambv not to be pushy/disrespectful, but is that soon, actually soon? 😅

[ambv]

Right. Surely before Christmas, likely not in November though.

[Aareon]

Looking forward to this as pipenv screams if you try to install without the --pre flag

[massenz]

It would really be nice, as I currently have to do this in pipenv (I don't want by mistake to allow other "pre-release" packages):

black = "==18.9b0"

and it's not really a great practice (as it also prevents me from automatically getting the latest and greatest).

Thanks for creating Black, though - super-awesome!

[Aareon]

I agree. Being able to streamline Black with other development tools is a huge plus. Black is currently a MUST in all of my projects.

[lig]

@ambv Merry Christmas!:)

[dimaqq]

Please? 🙏

[dyve]

See also
alanhamlett/pip-update-requirements#23 (comment)

This means we cannot update black in requirements.txt with pur.

A non-beta version would be much appreciated.

[Utsav2]

Black at HEAD has a fix for issue 282, and we can't beta test it at Dropbox until there's a release with that issue fixed. Please consider creating a new release soon.

[Peque]

@ambv Friendly ping. 😇

[fernandezpablo85]

@ambv friendlier ping

[max-wittig]

@ambv even friendlier ping :P

[hugovk]

Give the last beta a serious spin for the remainder of March! I'll tag the first stable release in early April.

https://twitter.com/llanga/status/1106247630370283523

[dimaqq]

Cheers @hugovk , it does feel like formatting got pretty stable in black:
2 lines changed in 100KLOC codebase with the latest release :)

[tribals]

Any changes on this?

[zsol]

I hear @ambv loves making stable releases in April, so I have high hopes ;)

[ambv]

FYI, we are sprinting on Black at PyCon now with the target stable release at some point right after.

[max-wittig]

What's the status here? It's annoying to use/install a pre-release package 😞

[lig]

@WimYedema right. That is exactly what is happening;) Black is already the standard format for Python code in an enormous amount of projects. Black is more stable and usable than some libraries in Python's stdlib. I even changed a laptop and restored my Black sticker on a new one already. And still, we have it in a "pre-release" stage.
I'm starting to think that Black will be a legendary Python package that will never go out of a pre-release just for the sake of it.

P.S.: this issue is 3 years old already BTW...

[astrojuanlu]

I think I am addicted to the comments on this issue. The maintainers have repeatedly stated their point of view, and yet people keep begging (begging!) that black releases a stable version (clearly showing that they have not read such pronouncements) while acknowledging that they're using it regardless. Or, alternatively, they complain here that Pipenv can't handle beta packages correctly, which is hardly a black issue and more of a Pipenv issue.

Three years of useless ramblings and crazy ideas only for folks to stop seeing a teeny-weeny chr(98) letter at the end of the version string, as if this is going to bring world peace, end world hunger, and convince humans to stop putting pineapple on pizza!

Black maintainers: please never ever release a stable version. Keep the charade on. Not even in the face of Armaggedon. Never compromise.

[lig]

@ambv please, reopen this one.

I believe it has been closed because of Eventually fixes #517. in #2529.

[lig]

@ambv please, reopen this one.

I believe it has been closed because of Eventually fixes #517. in #2529.

[gsemet]

Hi. I have read and reread again this thread and I still do not understand why a non-prerelease version of black has not been released yet.
At least provide the option to the user. Keep "black" as it is but provide a "black-stable" package that allow your beloved users to not force version or allow_prerelease for package.

I use poetry, so this is not a problem for me. But I do not see why black would behave differently than any other python package (release... Pull Request... release.... and over and over).

[dimaqq]

@gsemet please release it to PYPI. call it gray or whatever 🖤

[hugovk]

https://pypi.org/project/gray/, https://pypi.org/project/grey/, https://pypi.org/project/blue/, https://pypi.org/project/tan/ and https://pypi.org/project/white/ already exist :)

[dimaqq]

Someone even made https://pypi.org/project/blacker/ which is black at some old version 😅

blackish is still free though!

[felix-hilden]

We appreciate the enthusiasm, but please note that we have defined a stability policy (#2394) and are planning a stable release. Any news will be announced here. In the meantime though, further comments don't really make the cogs turn any faster.

[dyve]

We appreciate the enthusiasm, but please note that we have defined a stability policy (#2394) and are planning a stable release. Any news will be announced here. In the meantime though, further comments don't really make the cogs turn any faster.

Agreed. No black humor please.

[gsemet]

https://pypi.org/project/blacker/

That's an option:

• get a pipeline triggered on any new version of package black
• convert the version XX.M.bP to XX.0M.P and rebuild the same package named black-let-It-go

[felix-hilden]

I'm pleased to announce that Black is finally non-beta software! 🎉 Here's the full changelog!

Going forward we'll follow our stability policy. Work continues as usual with bugfixes and enhancements, but style changes are now introduced under our new --preview CLI switch. This allows us to evolve Black's style without too much disruption to users that want consistency. The default style is updated yearly.

Thanks to our maintainers for orchestrating the efforts, especially to our most recent reinforcement Batuhan (@isidentical) who was responsible for our match statement support! A hearty thank you to all of our contributors for pushing Black forward, and to our users for being the reason we do it!

Thanks for sticking with us, it's time to close this issue!

[ambv]