Update instructions to install latest version of black

[imsahil007]

We can close #970 now.
This will ensure that user install the latest version from black Github repo

[imsahil007]

Should we close #909 as well?

[terriko]

Hm, I thought the problem was backwards to this -- it seemed like I had 20.8b1 (latest from pypi) installed, but it seemed like CI was using something else. I'd like to switch our CI (and pre-commit) use latest release (or I guess in this case latest beta release, but it's what's tagged as latest in pypi)

[imsahil007]

Hm, I thought the problem was backwards to this -- it seemed like I had 20.8b1 (latest from pypi) installed, but it seemed like CI was using something else. I'd like to switch our CI (and pre-commit) use latest release (or I guess in this case latest beta release, but it's what's tagged as latest in pypi)

Installing black from GitHub instead of PyPI is a temporary solution for this. But the user might need to update it every then and now. We can do 2 things right now:

1. Use the pre-commit hook without specifying any version(This will use github version of black). User will have to update black from GitHub every then and now as stated above.
2. Use a specific version of black and manually update it whenever a new stable version is updated on PyPI. We will also have to update the requirements.txt accordingly.

[terriko]

What I really want is for pre-commit to use the latest tagged release. I think this is likely closer to option 2, and in fact our current pre-commit specifies rev: stable which I thought would work because as far as both github and pypi are concerned, 20.8b1 is the stable release.

repos:
-   repo: https://github.com/python/black
    rev: stable
    hooks:
    - id: black

At a guess, the problem is that pre-commit doesn't see something with the version 20.8b1 as a stable release because under pep 440 that would be a beta. We'll to dig deeper into pre-commit to see if there's a keyword like "stable" that we could use for "latest beta" if that's what it thinks the current released version is.

[imsahil007]

According to this, we are using the latest beta release 20.8b1 only

[terriko]

Whoops, this was hit on the wrong PR, sorry.

[terriko]

Revisiting this: So if CI is using 20.8b1, changing our docs to recommend anything other than that is going to lead to frustration. I guess I'm going to go with the solution in #970 for now, and we'll see if it changes frequently enough to be annoying. I'd still really like a solution that told pre-commit to use the latest release instead of a specific tag, but as best I can tell it doesn't support that at this time.