iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add an open issue about `marker` and `needs` per package version

This commit is contained in:
Brett Cannon 2021-08-16 14:07:32 -07:00
parent 2147ddc995
commit 2d7c608983
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
pep-0665.rst
View File

@ -1006,6 +1006,21 @@ lived along side ``needs`` and would only be specified if it would
differ from what is specified in ``needs``.
-----------------------------------------
Providing `marker` and `tags` per Package
-----------------------------------------
It has been suggested to allow for the `marker` and `tags` keys as
found in the `[metadata]` table in `[package]` tables as well. This
would allow lockers to specify when a version of a package should be
considered. This also has the potential for lowering computational
costs for installers by assisting them in knowing when to remove a
package version from consideration.
This does, though, somewhat duplicate environment markers being kept
in the `needs` array.
===============
Acknowledgments
===============