Zanie Blue
Zanie Blue
> especially because the python-build-standalone Windows executables don't otherwise include the Python version numbers in their names. As far as I know, we're just following the standard Windows build behavior...
cc @zooba if you care to weigh in on what is best here.
Great thanks for the input! I'll rename it upstream — makes life a bit easier anyway. I'm not sure what the best approach will be to address your `uv run`...
@colesbury I added https://github.com/astral-sh/uv/pull/8310 as a temporary workaround in uv — just much easier to land a quick change here than upstream. I'll try to look into that `uv python...
Will be fixed in the next upstream release too
Tragically, changing the path upstream post-build breaks virtual environments. See https://github.com/indygreg/python-build-standalone/issues/405 Any insights would be appreciated!
I don't think matching `pip`'s output is important here, I'd lean towards retaining the current ux.
I have no idea, that's very weird.
Thanks for the report. cc @konstin
Is this a duplicate of https://github.com/benfred/py-spy/issues/675