Zanie Blue
Zanie Blue
In the same way we let you put versions in that file, but not the name of an environment. It sounds like you put an environment name in there which...
I don't see using an environment name in the version file in the pyenv documentation. Regardless, I don't think it's a use-case we can support.
I see, thanks. It sounds like this is an extension of `.python-version` files as defined by `pyvenv` specifically for `pyvenv-virtualenv`?
The test is failing because you changed version file parsing to split on within-line whitespace so something such `>3.8, 3.8,` which changes the snapshot: ``` 3 │-Updated `.python-version` from `>3.8,...
I'm still not excited about making this change. It relies on some specific third-party behavior and we generally try not to integrate with third-party Python discovery mechanisms here.
I believe https://github.com/astral-sh/uv/pull/12909 should cover the use-case you have here, without encoding knowledge of `pyenv-virtualenv`.
This has the same cause as https://github.com/astral-sh/uv/issues/13316
I don't think gating single rules behind additional configuration is appropriate for us
thank you!
I'm interested! Sorry for the lack of reply — got lost / I don't have great answers. 1. Whichever is fine. I'm happy to clean up some Rust or review...