-
Notifications
You must be signed in to change notification settings - Fork 959
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
Timestamp metadata not parsed from private package index. Unexpected behavior for --exclude-newer
option
#10394
Comments
Are there upload dates in the html or json output of azure? |
Yes, of course. The timestamps are present and displayed in the Azure page. Sorry I forgot to mention it. |
Can you include a redacted example of the HTML page or JSON response, so we can see the upload date format? E.g., for |
I see from @charliermarsh's clarification that I may have misunderstood the first question by @konstin. The page However, the output of
|
To support |
@alfredocarella if you are able to open a ticket with Azure these are the relevant specifications they should implement:
Which were added in PEP 691 and PEP 700. |
The package upload timestamp appears to be missing when searching a private (Azure artifacts) package index.
This prevents the option
--exclude-newer
from being used correctly.Running this command
uv run --verbose --no-env-file --default-index https://[email protected]/my-organization/_packaging/my-feedname/pypi/simple/ --keyring-provider subprocess --exclude-newer 2025-01-06 -s minimal_script.py
produces the following output:
The contents of minimal_script.py are:
The script runs correctly when the option
--exclude-newer 2025-01-06
is removed.The text was updated successfully, but these errors were encountered: