Chris Pryer

> The reading back of the lock comments would still have to be honored. Likewise the legacy `pre: true` flag would have to updated. Look at `LockOptions::restore` for what I...

I'm going to close this for now. I won't be able to get back to this until the 15th.

I couldn't reproduce this on my windows machine with 0.28.0 (`main`). ``` ❯ rye --version rye 0.28.0 commit: 0.27.0+8 (2111778b3 2024-02-28) platform: windows (x86_64) self-python: [email protected] symlink support: false uv...

FWIW I could not repro the latest example ``` @cnpryer ➜ /workspaces $ rye init xyz success: Initialized project in /workspaces/xyz Run `rye sync` to get started @cnpryer ➜ /workspaces...

For posterity, Konsti [suggested to use `maturin` for inspiration](https://github.com/mitsuhiko/rye/pull/86#issuecomment-1536309461) if anyone is interested in taking that up.

Thanks for checking it out! If there's interest in this I'd like to: 1. PR [`--non-interactive`](https://github.com/mitsuhiko/rye/pull/759#discussion_r1501693285) - User only directly interacts with Rye. 2. Use something like `resolve_credentials(cmd)` to clean...

To be honest I think the best way to leave this would be to specifically only dish out for Twine's keyring support and then [do something more robust](https://github.com/mitsuhiko/rye/pull/759#issuecomment-1962727092). I'm not...

> Maybe also worth considering ditching `twine` for `maturin`? If that's where you want to go with it. I do like the token experience we're going for, but if there's...

> I think this is a good start. Is there any chance you could add basic tests for this? Maybe by mocking up a dummy endpoint. Yea I looked at...

> Would be great to add a basic test in. This is the type of code that is easy to break. I tried to crank that out real quick. I...