From 405cab5c9651ded79d21630e7e47cd7ef52845b1 Mon Sep 17 00:00:00 2001 From: Oz Tiram Date: Thu, 30 Apr 2026 15:39:14 +0200 Subject: [PATCH] Update docs/pipfile.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/pipfile.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/pipfile.md b/docs/pipfile.md index 78e84cc00..1660dd97a 100644 --- a/docs/pipfile.md +++ b/docs/pipfile.md @@ -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 `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 `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.