Remove setuptools as a runtime dependency #479
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
setuptools
is not actually used in any runtime code. Onlyliccheck
duringlint
uses it forpkg_resources
, which has long been deprecated (and is moreliccheck
's problem to migrate away).liccheck
also does not yet officially support Python 3.12, otherwise I would think they would explicitly specify thesetuptools
dependency themselves.The only reason why
setuptools
would be present in a runtime environment is forpkg_resources
, whose functionality has been replaced bypackaging
and theimportlib
suite. Otherwise,setuptools
pollutes the environment, particularly at the operating system distribution level. Many Python packages have not adopted PEP 517 and still executesetup.py
directly, functionality thatsetuptools
deprecated in 58 and no longer supports after. Multiplesetuptools
cannot exist in the same environment.