Zanie Blue
Zanie Blue
It's a bit of a bummer that in all the snapshot changes here we just end up repeating the URL.
Ah `pyw` is "Windows only", we can improve the error message here. Or.. just invoke the `python` interpreter (which I think could be correct?)
Just let us know here or in a draft pull request if you need any help!
There's also an argument beyond conformance, i.e., that removing support for, e.g., xz, reduces supply chain attack surfaces (which is the main reason we care in uv and is noted...
Regarding (2) though — if pip supports unarchiving arbitrary source trees, then we're in a tough spot from a perspective of reducing supply chain surface area.
I agree this issue is intended to focus on source distributions exclusively. I'm just also noting that the _motivation_ of reducing supply chain attack surface may not be applicable to...
Makes sense to me!
My understand is that the shebang is consistent with rest of the ecosystem, though I could be wrong. Are there other tools that use `SHELL` here? Separately, I don't think...
> Doesn't seem like /bin/sh is used anywhere as a const in the rest of the ecosystem. Can you provide an example? The code you link to has a reference...
Sounds like you're just looking for `--upgrade-package`? Why is it a big deal to specify the name twice? Isn't it harder for users to do `uv pip install --upgrade --upgrade-strategy...