Fix pyoxidizer_binary
to support python_distribution
targets that depend on others (Cherry-pick of #14620)
#14626
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.
It's very common for one
python_distribution
to depend on another, e.g.pantsbuild.pants.testutil
depends onpantsbuild.pants
. We can easily support that by having the user specify all necessarypython_distribution
targets in thedependencies
field.A fancier implementation would calculate for you automatically what dists a
python_distribution
depends on. But that's more complex than it sounds! Note that the dependency is not expressed explicitly via thedependencies
field, but instead via very complex logic insetup_py.py
; we'd need to leak that implementation here, or scan the generatedinstall_requires
. Pants's support for PEP 517 also makes things complicated. So, instead, for now at least, we go with the simple workaround.[ci skip-rust]
[ci skip-build-wheels]