PublicArchive/pipenv
2
0
Fork 0
mirror of https://github.com/pypa/pipenv.git synced 2026-05-06 08:26:42 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update docs/pipfile.md

Browse Source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Oz Tiram
2026-04-30 15:39:14 +02:00
parent 71a05b917e
commit 405cab5c96
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pipfile.md
+5 -3
View File
@@ -222,9 +222,11 @@ Restricts the resolver to package versions that were uploaded to the index at le
the specified number of days ago. This gives newly-published releases time to be
vetted by the community before they are automatically pulled into your project.
The value must be a string in `<int>d` format (e.g. `"30d"` for 30 days). Internally
pipenv translates this to pip's `--uploaded-prior-to P30D` flag, which is only
effective against indexes that expose upload-time metadata as described in the
The value must be a string in `<int>d` format (e.g. `"30d"` for 30 days). Internally,
pipenv computes a cutoff datetime in UTC (`now - N days`) and passes that cutoff to
pip's uploaded-prior-to filtering. Pip also supports duration-style values such as
`P30D`, but pipenv's behavior here is based on a concrete cutoff timestamp. This is
only effective against indexes that expose upload-time metadata as described in the
[Simple Repository API](https://packaging.python.org/en/latest/specifications/simple-repository-api/).
When the index does not provide upload-time metadata (e.g. most private mirrors) the
setting is accepted but has no filtering effect.