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.