-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Implement --uploaded-prior-to
#13625
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.
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
Open
notatallshaw
wants to merge
4
commits into
pypa:main
Choose a base branch
from
notatallshaw:uploaded-prior-to
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+700
−13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
61fa50c to
716ee0d
Compare
Member
Author
|
Okay, this is again ready for review or approval, though I appreciate if no one will have time before 25.3, I will move to 26.0 if it remains unmerged before release. |
This was referenced Nov 4, 2025
716ee0d to
255fe19
Compare
…-time`, pass to `SubprocessBuildEnvironmentInstaller`
255fe19 to
38e3992
Compare
38e3992 to
1f6c9b8
Compare
Comment on lines
+335
to
+338
| This option only applies to packages from indexes, not local files. Local | ||
| package files are allowed regardless of the ``--uploaded-prior-to`` setting. | ||
| e.g., ``pip install /path/to/package.whl`` or packages from | ||
| ``--find-links`` directories. |
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth mentioning that VCS requirements are similarly unaffected by --uploaded-prior-to?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #6257
Supplants #12717 & #13520 (because I accidentally broke that PR)
Design Choices:
Option Name & Semantics - "uploaded-prior-to" was chosen to match semantically with an exclusive upper bound in both the "date" and "datetime" format, e.g.
--uploaded-prior-to 2025-01-01includes only packages uploaded prior to2025-01-01 00:00:00(i.e., 2024 and earlier): #13520 (comment)Timezone - Accepts ISO 8601 datetime strings, defaults to local timezone if unspecified. Documentation recommends explicit UTC (Z suffix) or UTC offset for reproducibility: #13520 (comment)
Error Handling - Fails immediately if a package index doesn't provide upload-time metadata. File system packages (local directories, wheels, etc.) are unaffected - this only applies to remote indexes: #13520 (comment), so you can specify local packages that depend on remote packages and filter those remote packages by