black and ruff are now in plain conflict

[benoit74]

See openzim/cms#263 (comment)

I've experienced the same on Zimfarm

@rgaudin I remember you mentioned the same kind of issue at some point

Should we adapt our convention and simply drop black now that ruff has made a lot of progress? Is there any added value left in black?

[rgaudin]

Every project I touched recently, I've:

• removed black completely
• updated tasks.py (removed black step, use ruff check)
• updated workflows (remove lint-black step)
• updated pyproject.yaml to used exploded options style ([tool.ruff.format])
• remove pre-commit hook (been more of a pain than a help)

I've also been experimenting with just instead of invoke but it's not conclusive.
Main change is that I've been using uv more but I haven't settled on a new setup so that's why I didn't share those changes yet

[benoit74]

I'm still quite attached to pre-commit hooks, it works quite well on my side (besides when black and ruff conflicts obviously). I propose to move this discussion aside. Potential move to uv is already mentioned in #54

[benoit74]

@elfkuzco would you like to prepare a PR which drop black from the bootstrap so we are all on the same page regarding what is the new "standard" for Python projects?

[benoit74]

I'm still quite attached to pre-commit hooks, it works quite well on my side (besides when black and ruff conflicts obviously). I propose to move this discussion aside.

I just realize that you were probably speaking only about black pre-commit hook, not all hooks ... sorry