You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: peps/pep-0780.rst
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -304,8 +304,8 @@ ecosystem tools, especially those which attempt to support examination of data
304
304
in ``pyproject.toml`` and ``requirements.txt``.
305
305
306
306
In particular, current tools generally work with a fixed list of environment
307
-
variables, either in their own implementation (e.g. `uv<https://github.com/astral-sh/uv/blob/86e7b2e97a193ce3f506804be4c41c611191fa72/crates/uv-pep508/src/marker/tree.rs#L170>`_)
308
-
or via an established package like `pypa/packaging<https://github.com/pypa/packaging/blob/8f13a4309aa620bf643cd508304f783b456e8c49/src/packaging/_tokenizer.py#L63>`_ (e.g. pip).
307
+
variables, either in their own implementation (e.g. `uv`_) or via an
308
+
established package like `pypa/packaging`_ (e.g. pip).
309
309
Hence, it is principally impossible to add any new environment markers without
310
310
making new packages using these markers incompatible with older versions of
311
311
these tools.
@@ -415,6 +415,8 @@ Footnotes
415
415
particularly on platforms that allow the execution of either kind of binary.
0 commit comments