-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
PEP 631: Dependency specification in pyproject.toml based on PEP 508 #1571
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.
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
Conversation
The CI fails because it doesn't have Pygments to handle the It can be added here: Line 10 in ddc388e
|
@hugovk Thanks! |
You will need a sponsor from the PyPA for this PEP; see PEP 1. |
I should also mention you grabbed a PEP number before you were assigned one. 😉 You can put in 999 for now and when your PEP is ready to be merged we will give you the number. |
Ah, I had no idea how that worked. Will do! |
pep-0999.rst
Outdated
@@ -0,0 +1,149 @@ | |||
PEP: 999 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can claim a PEP number now. Change this to PEP 631 and I think we can merge this.
Co-authored-by: Paul Ganssle <[email protected]>
Done! |
…ython#1571) * PEP 631: Dependency specification in pyproject.toml
Rendered: https://github.com/ofek/peps/blob/631/pep-0631.rst
Discussion: https://discuss.python.org/t/pep-999-dependency-specification-in-pyproject-toml-based-on-pep-508/5018