[Request] Update installation methods

[yozachar]

Edit

Outdated comment

Linux and MacOS users can use asdf to install rye.

$ asdf plugin add rye
$ asdf install rye latest
$ asdf global rye latest
redirect url: https://github.com/mitsuhiko/rye/releases/tag/0.5.0
$ rye --version
rye 0.5.0
commit: 0.5.0 (5f96294de 2023-05-31)
platform: linux (x86_64)
self-python: [email protected]
symlink support: true

Windows users can use scoop as soon as this PR (https://github.com/ScoopInstaller/Main/pull/4849) is merged.

$ scoop install rye

This can be included in the docs here:

https://github.com/mitsuhiko/rye/blob/b4caf51f3648e6c24ad047438a75608d4118e378/docs/guide/installation.md?plain=1#L19-L44

These installation methods will automatically take care of adding rye shims to the path.

See: https://github.com/mitsuhiko/rye/issues/278#issuecomment-1696644586

[sitiom]

See https://repology.org/project/rye/versions for the complete list of packages so far:

[mitsuhiko]

The challenge with alternative installation methods is that I neither control them nor have the capacity to support them at the moment. I would need to figure out how to best approach this as I have little experience with that.

[sitiom]

Perhaps you can add a separate "Third-party packages" section with a disclaimer and point to the Repology list.

[yozachar]

The challenge with alternative installation methods is that I neither control them nor have the capacity to support them at the moment. I would need to figure out how to best approach this as I have little experience with that.

Having a rye GitHub org, may help, ref: https://github.com/mitsuhiko/rye/discussions/46 You can create a repo called distributions which tracks status on repology / third-party etc.

[doolio]

These installation methods will automatically take care of adding rye shims to the path.

Using asdf and this was not the case for me. I still had to manually add them to my path.

[yozachar]

Using asdf and this was not the case for me. I still had to manually add them to my path.

Did you try asdf reshim after installation, also, are you sourcing asdf before starting your shell?

---

I used rtx an alternative to asdf found it far more robust.

$ rtx i rye@latest

---

But I suspect, that anyone would want to fiddle with multiple versions of rye, unless they are developing the same. Instead since rye publishes releases on GitHub, I recommend using bin to manage binaries.

$ bin i https://github.com/mitsuhiko/rye 
   • Getting latest release for mitsuhiko/rye

Multiple matches found, please select one:

 [1] rye-x86_64-linux.gz
 [2] rye-x86_64-linux.gz.sha256
 Select an option: 1
   • Starting download of https://api.github.com/repos/mitsuhiko/rye/releases/assets/123323774
7.39 MiB / 7.39 MiB [--------------------------------------------------------------------------] 100.00% 1.46 MiB p/s 5s
   • Copying for [email protected] into /home/user/.local/bin/rye
   • Done installing rye 0.12.0

$ rye --version                                                                             
rye 0.12.0
commit: 0.12.0 (f5525c985 2023-08-27)
platform: linux (x86_64)
self-python: [email protected]
symlink support: true

[doolio]

Did you try asdf reshim after installation, also, are you sourcing asdf before starting your shell?

No and Yes.

asdf reshim will simply reshim the asdf rye shim not the shims python and python3 provided by rye.

The rye docs state you have to manually add its shims to your PATH and it is still necessary to do that even if installing with asdf. A potential issue in doing that though is if you also use asdf-python you may not be using the python version you want depending on which shim comes first on your PATH and whether you are in a rye managed python project or not. To avoid any issues it is important to ensure the python version within your virtual environment is first on your PATH when your environment is activated.

I used rtx an alternative to asdf found it far more robust.

Thanks I was not aware of rtx. I might consider it as an alternative but asdf has been working well for me.

But I suspect, that anyone would want to fiddle with multiple versions of rye, unless they are developing the same.

I presume you mean would not want to fiddle with multiple versions of rye. I agree. Thanks also for making me aware of bin I may also consider it.

[sitiom]

Why is this issue closed?

[yozachar]

The official installation instructions seems sufficient for an overall new user. Anybody else well acquainted with packaging, probably always checks repology.

Apart from that I did not find rtx (esp. asdf) as suitable candidates to manage rye. bin seems fine, but is less known. So I thought maybe adding more installation methods isn't worth the apparent confusion it might cause new users.

But after seeing this:

Adding another tab titled Using Package Managers might not be a bad idea after all.