Chris Pryer

If I have time later I'll finish up a first-pass. I can use test.pypi.org to manually test the changes. I wouldn't do anything with that branch yet. It's definitely not...

FWIW I wasn't able to repro this in a fresh environment ``` @cnpryer ➜ /workspaces $ rye init rye-test success: Initialized project in /workspaces/rye-test Run `rye sync` to get started...

I should have mentioned that I also set up `pyenv` and installed a Python distribution to use. ``` @cnpryer ➜ /workspaces/rye (main) $ which pyenv /home/codespace/.pyenv/bin/pyenv ```

> One of the things that I really need help with is improving the documentation. I tried to make some improvements now by documenting the individual commands, but there is...

If you want this sooner rather than later I can knock it out. Otherwise I don't want to take away from potential first-timers a good first issue.

IMO a *Publishing* page in the user guide is probably sufficient. Otherwise this is super self-contained. If a new page is overkill it'll be easy to move elsewhere. No harm...

This would actually be nice for me assuming `poetry export` gets me what I'd want here. Ideally I could export to requirements and then `rye init --import` all my `poetry`-managed...

How does this sound? 1. Attempt to read setup.cfg metadata 2. Attempt to update metadata with setup.py metadata (uses hack) 3. Resort to requirements.txt and requirements-dev.txt files if needed 1...

> where we support `setup.py` Do you mean allow for the package to build and then pull its metadata from the distribution? I like that better tbh. > Not sure...

Wanted to report this here since it's relevant. I might create another issue for it to PR it if I can get some time. If you add dev dependencies to...