Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid naming schemas with specific PEP numbers #7

Merged
merged 3 commits into from
Feb 10, 2022
Merged

Avoid naming schemas with specific PEP numbers #7

merged 3 commits into from
Feb 10, 2022

Conversation

abravalheri
Copy link
Owner

Address #6

@abravalheri
Rename schema files to avoid mentioning PEP 621
afcf3a0 
Although PEP 621 introduced the `project` table in the `pyproject.toml`
file, that table will evolve with time incorporating other PEPs, so we
should avoid associating the schema with a single PEP name.
@abravalheri
Improve pyproject schema to focus on the living standard instead of PEPs
76714a6
@abravalheri
Adjust implementation to work with the new files/ids
dd1fa03
@abravalheri abravalheri linked an issue Feb 10, 2022 that may be closed by this pull request
Avoid naming schemas with specific PEP numbers #6
Closed
@abravalheri abravalheri merged commit 36d57d8 into main Feb 10, 2022
@abravalheri abravalheri deleted the issue-5 branch February 10, 2022 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Avoid naming schemas with specific PEP numbers
1 participant
@abravalheri