Add setuptools and/or wheel to requirements/host when used

[jakirkham]

In preparation for changes in pip's packaging as discussed in issue ( conda-forge/pip-feedstock#124 ), it would be good if we could detect the usage of setuptools and/or wheel in Python packages and add them to requirements/host if they are needed

[jakirkham]

cc @beckermr

[beckermr]

yes we can add a mini-migrator but we'll need to figure out a decent way to understand what we need to add - it is not clear to me when we need setuptools-only vs both setuptools+wheel.

[jakirkham]

To the extent that Python packages declare these dependencies in their pyproject.toml's build-system.requires, grayskull can pick them up and add them

Is this something that depfinder checks?

[beckermr]

depfinder only detects imports and so would miss this in some cases.

[jakirkham]

Can you please share some examples? Identifying the edge cases will help us come up with a better solution

[beckermr]

Oh right sorry. Here are the ones I am thinking of. None of them mean we cannot do this, but it will require thought+code.

• grayskull fails for w/e reason
• the recipe uses flit, hatchling, meson etc. as a build backend
• the project only uses a pyproject.toml and so depfinder won't check anything since it only looks at python imports
• there are surely multioutput recipes with odd edge cases

[jakirkham]

As an interesting example

lda gets flagged as needing setuptools: conda-forge/lda-feedstock#12

AFAICT it is only used in lda's cibuildwheels tests

[beckermr]

Even more interestingly, setuptools is already in host in that recipe. :/

[beckermr]

Ahhhh. The bot flagging that is not related to depfinder or grayskull but is because it detected that package in host.