Skip to content

Conversation

j178
Copy link
Contributor

@j178 j178 commented Apr 17, 2025

Summary

I added a subset of the Python downloads metadata json file for tests.

This PR also fixes a issue where using --only-downloads with --all-arches, --all-arches is not honored.

I added a subset of the Python downloads metadata json file for tests.
This PR also fixes a issue where using `--only-downloads` with `--all-arches`, `--all-arches` is not honored.
@j178 j178 force-pushed the list-only-downloads-all-arches branch from da51176 to 91137f2 Compare April 17, 2025 21:10
@@ -0,0 +1,674 @@
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be here?

Copy link
Member

@zanieb zanieb Apr 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see it's being used for the test case. Interesting 🤔 I'm worried about maintaining these. Do we need a subset? If so, should it be much smaller? Can you say more about the choice?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need a fixed subset to keep things stable; otherwise, the tests fall apart every time we sync the latest Python versions.

So, I’m making sure the subset includes a prerelease, a freethreaded variant, different patch versions of the same minor version, and different minor versions. This way, we’ve got a pretty thorough test case.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm.

I'm not sure if I mind if the snapshots need updating when the available versions change.

My concern is that the snapshot doesn't capture the reality for most users, which makes it less valuable and more likely for us to accidentally ship regressions.

Comment on lines 81 to 82
} else if all_arches {
base_download_request.fill_platform()?.with_any_arch()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a bug fix?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, it'd be better to do this separately so it can be listed in the changelog.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extracted it to #12953

@j178 j178 force-pushed the list-only-downloads-all-arches branch from 91137f2 to b580da0 Compare April 17, 2025 21:19
@j178 j178 force-pushed the list-only-downloads-all-arches branch from b580da0 to d1ce394 Compare April 17, 2025 21:24
j178 added a commit to j178/uv that referenced this pull request Apr 17, 2025
@zanieb
Copy link
Member

zanieb commented Apr 21, 2025

Note this overlaps with #12381 which I forgot to follow-up on after #12381 (comment).

j178 added a commit to j178/uv that referenced this pull request Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants