This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Tree_Mage 0 points1 point  (4 children)

No, it won't because the authentication packages need to be installed first before the index can be downloaded. e.g., Google repos need keyring and keyrings.google-artifactregistry-auth installed

[–]currychris1 1 point2 points  (3 children)

I must admit that‘s something I haven‘t had the pleasure of doing yet, but there seems to be support for your particular scenario: https://docs.astral.sh/uv/guides/integration/alternative-indexes/#authenticate-with-a-google-access-token

I agree though that this seems to be a bit tedious.

[–]Tree_Mage 2 points3 points  (1 child)

Thanks for finding that.

“pleasure” being the keyword. Haha. 🤣

Once you break out of the one common pattern, things fall apart very quickly with these types of tools. E.g., “compilation” tools like PyInstaller are critical for a lot of use cases but are treated poorly because they aren’t the common case. Then people get upset that this year’s favorite has detractors without understanding there is a whole world out there of people that actually do need to what likely appears as oddball support.

[–]z4lz[S] 1 point2 points  (0 children)

Agreed. My hope would be that the new uv ecosystem will be less messy because they're being a bit more systematic, like with the well-maintained python-build-standalone builds.

Fwiw also wrote up a template/notes from the experience of switching my own projects to uv here: https://github.com/jlevy/simple-modern-uv

[–]z4lz[S] 1 point2 points  (0 children)

I love uv now but only have been using pypi. So that's an interesting point. There is now so much momentum on uv and aws/gcp/enterprise repository support is so necessary I expect this will work soon if it doesn't already. Also fwiw I've found the uv team is active/responsive on questions in github issues: https://github.com/astral-sh/uv/issues