Alternative solution about sync_with_poetry HOT 3 CLOSED

Ok I see. +1 for the pre-commit.ci integration but since my system hook runs poetry run, which activates a virtual environment, I don’t think a lot of the problems with the system hooks don’t happen, eg I know exactly which mypy executable gets called in the example above.

from sync_with_poetry.

Yes. Personally, I prefer to rely on the pre-commit framework for many reasons, e.g., QA in CI/CD pipelines. As you mentioned, you can do the same job with poetry run in a local fashion. Maybe with an easier setup, but with some limitations.

from sync_with_poetry.

It depends on your needs. You can definitely work that way, but:

"[...] this defeats the purpose of the framework entirely, but it enable some amount of legacy compatibility in some use cases."

(read more about it in this SO answer by Anthony Sottile)

PS: System hooks do not play nicely with https://pre-commit.ci/ and you need to skip them

from sync_with_poetry.