Zanie Blue comments

Results 2953 comments of


                                            Zanie Blue

Bug: `uv venv` on windows cannot find python from pyenv

Thanks for the report. We have some bugs around our handling of `pyenv` shims right now. Windows is especially complicated for Python version discovery :(

support 'uv --completions' to generate a completions file for bash/zsh/fish/powershell

Thanks this seems reasonable to add. We'd probably want to mirror whatever we do in Ruff.

`uv pip compile pyproject.toml` ignores dependencies declared in `setup.cfg`

@sbidoul I don't think so, that issue uses a `dynamic` value in the pyproject.toml as a hint to reinstall. Here we need to add PEP 517 calls to determine dependencies...

uv fails to build uWSGI when run from inside virtual env

This looks like it should be fixed by #1667

I expected `--resolution=lowest` to imply `--reinstall` for an existing package

We could also consider displaying a warning? That might be hard to do well though.

Simplified worker monitoring and restart, without gunicorn.

> 2. Answer the question: why this shouldn't be an opt-in feature? It seems like advanced monitoring should be opt-in and simple "is alive" monitoring should be the default since...

Rename string AST nodes

@dhruvmanila is this still relevant?

Add an `--exit-non-zero-on-fix` equivalent to the formatter.

> We could either to ruff format --exit-non-zero-on-fix (undecided on the name of the flag) without using check. However, the option would be incompatible when using with --check or --diff....

Add an `--exit-non-zero-on-fix` equivalent to the formatter.

Hm so `ruff format` is all you should need in pre-commit? Having pre-commit tooling check for differences makes a lot more sense than adding more exit code flags to Ruff.

Add an `--exit-non-zero-on-fix` equivalent to the formatter.

Good to hear it works :) I don't think this is justified then, I'm not sure what use-case would require this behavior.