Mark field values from __defaults__
as being a default value.
#20950
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.
Part 2 of 2 fixes #20947. (Part 1: #20949)
When providing default values using
__defaults__
for Python source globs, they are now treated as a default value, rather than a explicit value. The implication is on how pants treats multiple globs for the two cases. For defaults, as long as any glob matches an existing file, all is well, where as for explicit globs, all of them must match existing files.This was problematic when overriding the default source globs for the
python_sources
target for instance to make it recursive, as the defaults list many globs, some of which may not be applicable.Now, the experience augmenting the default globs are seamless (no more unmatched globs issues):