Zanie Blue comments

Results 2953 comments of


                                            Zanie Blue

.lock file causes conflict when installing python into a shared directory

Interesting. I'm not sure what we can do to fix this, but it seems worth trying to.

.lock file causes conflict when installing python into a shared directory

Oh it shouldn't persist across operations, afaik. Yes it's a file used for exclusive access, e.g., https://github.com/astral-sh/uv/blob/f0659e76cf215480d30d554118961c7c59ab3e2b/crates/uv-tool/src/lib.rs#L142-L145

.lock file causes conflict when installing python into a shared directory

Yeah I think you're right. Do we need to create the file with different permissions when we're in a globally writable directory?

It doesn't work on Alpine Linux（Actually in iSH app）

Thanks for the issue. We do support Alpine (ref #1392) but perhaps not on i686. Could you share the output with `RUST_BACKTRACE=1`?

It doesn't work on Alpine Linux（Actually in iSH app）

@lmBored how are you installing uv? Can you reproduce in a Docker image?

Wrong `python_full_version` in `uv.lock`

Generally it's expected for these markers to be disjoint. See the documentation on forking at https://docs.astral.sh/uv/reference/resolver-internals/#forking

Wrong `python_full_version` in `uv.lock`

Related #6150

Add an option to `uv run` to run a `.py` script with `pythonw.exe` instead of `python.exe`

We could parse the metadata with `pythonw myscript.py`, I think? Alternatively, we can provide a `--script-exec` option that we use to execute scripts per https://github.com/astral-sh/uv/issues/6542#issuecomment-2307709992

Add an option to `uv run` to run a `.py` script with `pythonw.exe` instead of `python.exe`

We added a `--script` flag in #7739 but we don't have a `--gui-script` flag — which would be Windows-only but reasonable to include, I think.

Add an option to `uv run` to run a `.py` script with `pythonw.exe` instead of `python.exe`

Yep this is implemented, sorry!