Chris Pryer
Chris Pryer
> I want to give this some priority. I think for now I will focus mostly on getting it running in CI somehow. That is > > 1. use `RYE_TOOLCHAIN`...
> a more reliable mechanism to disambiguate Would that just be something to signal to `rye` what it is? Like with bin/lib using `cargo`?
So I actually think this is a good call-out. This could become confusing to users. > The first priority is .python-version under workspace. Second priority is requires-python in pyproject.toml ....
Understood, but maybe what makes this a little tricky today is that there are a number of ways to configure this. So which do you prioritize and why? And then...
I really like this idea, but wouldn't it be wise to publish a public API after the project has been somewhat stabilized? Especially the parts of Rye that leverage the...
So far this comes to mind as a potential problem. ``` rye add --pre ```
> I really do not like if a parameter takes optional args. i think it would be better to say `--pre` means `--prerelease=allow` and to have a separate `--prerelease` parameter....
> For what it's worth, in `uv` we have `--prerelease=allow` etc., but we just added a hidden `--pre` alias for `pip` compatibility that's mutually exclusive with `--prerelease` and means `--prerelease=allow`....
For reference https://github.com/astral-sh/uv/pull/2049
I'm starting to spend more time on this one. In order to finish this I want to understand Rye's locking a little more. I'm not a pip-tools user, so I'll...