-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
PEP 633: Exploded dependencies for PEP 621 #1595
PEP 633: Exploded dependencies for PEP 621 #1595
Conversation
* Allow environment markers as keys * Add white-space before marker separator in PEP 508 conversion * Add note on reason for marker key transformation * Add note on 'extra' marker
This reverts commit 375aea5.
* Convert optional-deps to table of reqs with extra key * Fix optional-dependencies in docker-compose example * Add note on 'for-extras' key
* Add PEP 508 compatibility examples Initial set of examples demonstrating compatibility with PEP 508. * Fix typo in example version constraint * Add a note for version only dependency * Add missing new line * Update vcs examples * Fix markers example * Fix missing markers * Replace for-extras with for-extra
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.
The PR doesn't have the "let maintainers make changes" checkbox set, so I can't merge these final changes. Add these and then I can merge the PEP!
pep-9999.rst
Outdated
- Easy initial validation via the TOML syntax. | ||
|
||
- Easy secondary validation using a schema, for example a `JSON Schema`_. | ||
|
||
- Potential for users to guess the keys of given features, rather than | ||
memorising a syntax. | ||
|
||
- Users of multiple other popular languages may already be familiar with the | ||
TOML syntax. | ||
|
||
- TOML directly represents the same data structures as in JSON, and therefore a | ||
sub-set of Python literals, so users can understand the hierarchy and type of | ||
value |
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.
- Easy initial validation via the TOML syntax. | |
- Easy secondary validation using a schema, for example a `JSON Schema`_. | |
- Potential for users to guess the keys of given features, rather than | |
memorising a syntax. | |
- Users of multiple other popular languages may already be familiar with the | |
TOML syntax. | |
- TOML directly represents the same data structures as in JSON, and therefore a | |
sub-set of Python literals, so users can understand the hierarchy and type of | |
value | |
- Easy initial validation via the TOML syntax. | |
- Easy secondary validation using a schema, for example a `JSON Schema`_. | |
- Potential for users to guess the keys of given features, rather than | |
memorising a syntax. | |
- Users of multiple other popular languages may already be familiar with the | |
TOML syntax. | |
- TOML directly represents the same data structures as in JSON, and therefore a | |
sub-set of Python literals, so users can understand the hierarchy and type of | |
value |
Does this render appropriately with the newlines between the bullet points?
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.
make pep-9999.html
doesn't show any issues
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Dependency format proposal for PEP 621; see discussions at: https://discuss.python.org/t/pep-621-how-to-specify-dependencies/4599
Discuss at: https://discuss.python.org/t/dependency-specification-in-pyproject-toml-using-an-exploded-toml-table/5123
TODO:
Future: