Specify packages using include rather than exclude #62
+4
−8
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.
This avoids possible duplication if a wheel is built more than once from the same directory.
I ran into this when upgrading Debian's packaging of cssutils; we're currently in a transitional period where we're building for both Python 3.12 and 3.13, and this resulted in the second of the two wheels having a stray
build
directory. Usinginclude
rather thanexclude
avoids this, and seems to be simpler anyway.