Zanie Blue
Zanie Blue
The `python -m ...` issue should be fixed by #1667
This seems reasonable. We'll need to find a Rust equivalent to https://pypi.org/project/keyring/ Perhaps https://github.com/hwchen/keyring-rs
Thanks for the details! Much appreciated.
Yes this is intended to be working (and it's worked for me previously) — we'll investigate.
Looks to be working as intended with a uv virtual environment: ``` ❯ uv venv Using Python 3.9.6 interpreter at: /Library/Developer/CommandLineTools/usr/bin/python3 Creating virtualenv at: .venv Activate with: source .venv/bin/activate ❯...
Is there a simple reproduction to create a `pyenv` virtual environment for standalone usage? i.e. without installing their shim and doing auto-activation and all that?
I did not reproduce this with `pyenv` either ``` ❯ pyenv --version pyenv 2.3.35 ❯ pyenv virtualenv --version pyenv-virtualenv 1.2.1 (python -m venv) ❯ eval "$(pyenv init -)" eval "$(pyenv...
Oh interesting, thanks for digging into it @ngnpope!
I've opened a couple issues at https://github.com/astral-sh/uv/issues/4130 and https://github.com/pyenv/pyenv/issues/2979 to track this.
I think I'm going to close this one since we do correctly setup CLI entry points. Note the workaround here is to run `pyenv rehash` for _them_ to update their...