[Internal] Refactor how PythonToolBase
exposes requirements and interpreter constraints
#12356
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.
In a followup, the new
PythonToolBase.pex_requirements
will have the logic for how to load a lockfile:pants/src/python/pants/backend/python/lint/docformatter/rules.py
Lines 62 to 77 in bc46347
This will allow us to DRY setup of lockfiles.
[ci skip-rust]
[ci skip-build-wheels]