Skip to content

PEP 751: provide explanation for why path and url are optional #4109

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

Merged
brettcannon merged 1 commit into from
Nov 5, 2024
Merged

PEP 751: provide explanation for why path and url are optional #4109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions peps/pep-0751.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1083,6 +1083,19 @@ simply defaulting to the baseline in tools without considering the security
ramifications of that hash algorithm.


------------------------------------
Require a URL or file path for files
------------------------------------

Originally references to files were required, e.g., ``packages.sdist.url`` or
``packages.sdist.path``. But at least
`one use-case <https://discuss.python.org/t/pep-751-now-with-graphs/69721/34>`__
surfaced during discussions about this PEP where statically specifying the
location of files would be problematic. And in earlier discussions the idea of
the location being a hint wasn't preferred. Hence the PEP now makes the data
optional, but considers the locations accurate if specified.


-----------
File naming
-----------
Expand Down
Loading