Chris Pryer
Chris Pryer
> find a good way to pin to specific installations without throwing stuff into the .python-version file that other toolchains cannot work with What about doing something like ```toml [tool.rye]...
Yea this is what I've had my eyes on for this https://github.com/rust-cli/rexpect
I'd agree, but from what I can tell a lot of people find it useful. I think it's a UX thing. Like when you use `rye` you want to defer...
> Probably even for a more functional prototype rye would have to move away from pip-tools for something else This is raw but I thought it was worth sharing https://github.com/konstin/monotrail-resolve.
To get the ball rolling on this one I’m thinking: 1. Where/how install 2. Overview of features 3. Get Python with Rye 4. Start a project with Rye 5. Adding...
https://cnpryer.github.io/rye/user_guide/ I can submit this as a PR. I just used https://www.mkdocs.org/user-guide/deploying-your-docs/.
I'd love for `rye` to have opinions. If `rye` has opinions here less is probably better. This does sound like plugin territory. I see this like `rye` supporting any other...
Love it. How does this sound? 1. `rye publish` 2. "No access token found for \\nAccess token: \" IIRC that's roughly how `cargo` handles it.
Sounds like a plan. Just a heads up I'll be pretty busy until Thursday. If I can't pick this back up before then I'll tackle this into the weekend.
Just want to tag https://github.com/mitsuhiko/rye/pull/86/commits/f4ecb2e9dd6c5bec1fcbf1da1537fd2a9d0f2318 with https://packaging.python.org/en/latest/specifications/pypirc/