CadQuery's black fork

[greyltc]

This is about

cadquery/README.md

Line 214 in dadf151

- Run `black` from [our fork](https://github.com/CadQuery/black) to autoformat your code and make sure your code style complies

Would it be possible to switch this to the latest stable release of black going forward?

[jmwright]

@greyltc What is the reasoning behind switching away from the fork? If I remember correctly, one of the reasons we switched was because black had (or was causing) a dependency problem.

[greyltc]

Philosophically:
I understand the purpose of black is to ensure there's no ambiguity about how code should be formatted. Using a custom black fork defeats that purpose.

Practically:
I now have to build and run a special black version locally rather than rely on my OS package manger's provided latest stable prebuilt version (which works as expected with every other project I contribute to). Building black, [1408 commits behind] psf/black:main, for CadQuery is especially problematic because it depends on typed-ast, which is depreciated, unmaintained and no longer works with modern python versions.

[adam-urbanczyk]

For now no plans to change. The reason is to have stable formatting within the project.

Yes, you need to have a specific dev env (so pls don't use your OS package manger):
https://github.com/CadQuery/cadquery/blob/master/environment.yml

[adam-urbanczyk]

NB: it is quite explicitly documented in the README:

Create a conda development environment with something like:

    mamba env create -n cq-dev -f environment.yml