Skip to content

Conversation

@cdce8p
Copy link
Member

@cdce8p cdce8p commented Jan 22, 2026

Summary of changes

Allow the use of package-data for stubs only packages, see abravalheri/validate-pyproject#248.

Based on commit: abravalheri/validate-pyproject@c55827b

Pull Request Checklist

@cdce8p cdce8p marked this pull request as draft January 22, 2026 00:45
@cdce8p cdce8p force-pushed the update-validate-pyproject branch 2 times, most recently from d8443ff to 094d24b Compare January 30, 2026 15:47
@cdce8p cdce8p changed the title Update code generated with validate-pyproject Sync setuptools schema with validate-pyproject Jan 30, 2026
@cdce8p cdce8p marked this pull request as ready for review January 30, 2026 16:08
@cdce8p
Copy link
Member Author

cdce8p commented Jan 30, 2026

@abravalheri Would you mind taking a quick look at this one? I've sync setuptools.schema.json based on the latest changes in validate-pyproject and run tox -e generate-validation-code again.

@abravalheri abravalheri force-pushed the update-validate-pyproject branch from cc853a8 to 6f1e377 Compare February 3, 2026 11:09
@abravalheri
Copy link
Contributor

Thank you very much @cdce8p.

I modified the PR to use the latest version of validate-pyproject.
I have also added a check for the import-names(paces) field, which are correctly validated by validate-pyproject but not supported by setuptools yet.
I need to check if there is any other feature that has been incorporated in validate-pyproject but not supported by setuptools yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants