Clean up install vs. build requirements #34
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.
Summary
Clean up install vs. build requirements
wheel
andsetuptools
from package dependenciespackaging
from build dependencies; however, retain it as a packagedependency since it is a valid runtime dependency
Issue
When downstream packages depend on
mgrs
today, they havewheel
forced into their dependency graphs at install time. This occurs becausemgrs
as the upstream package currently lists two of its build requirements--wheel
andsetuptools
--as install requirements. To clean this up, we can keepwheel
andsetuptools
as valid build system requirements inpyproject.toml
, but we should omit them fromsetup.py
'sinstall_requires
section.