Pre-commit integration?

[reinout]

I'm using pre-commit in more and more projects. I was thinking... wouldn't a pre-commit integration hook be a nice addition to dependencychecker?

[gforcada]

We have thought on that during the Alpine City Sprint 2023, and what we thought is that, it might be not something you want to run on a per-commit basis, rather as a PR or scheduled CI? 🤔

Specially, given that there are some rough edges to be ironed out, for non-experienced developers it might confuse them even more.

But that was mostly with my Plone contributor hat on, generally speaking, indeed, having it as an option for anyone who wants to use it, it would be great 👍🏾

[gforcada]

Actually, as @mauritsvanrees mentioned in plone/meta#84 z3c.dependencychecker does not really need the actual dependencies to analyze the package, it needs an updated egg-info folder only.

I created a PR in plone/meta with this idea, see plone/meta#86 and it is really fast to run on my slow laptop, so I think it might not be a bad idea to add it as a pre-commit hook 👍🏾

On that PR in plone/meta I used build to generate the .egg-info folder.

We need to see how we can combine build and z3c.dependencychecker for pre-commit but I would say, let's try 😄

[mauritsvanrees]

build is something we should look at for zest.releaser as well, instead of calling python setup.py sdist/bdist_wheel/--version/etc