From my point, the tool is rather new, but it seems in good hands and goes into the right direction.
See https://alpopkes.com/posts/python/packaging_tools/

@return42 @Bnyro @unixfox @mrpaulblack and everyone else, what are your opinions on a tool like rye?

@return42 @Bnyro @unixfox @mrpaulblack and everyone else, what are your opinions on a tool like rye?

Looks promising .. Most python build, env and package tools are based on the python itself installed on a system ... since different python versions are installed on all systems this usually does not work well (e.g. pyenv).

I still have to take a closer look at Rye, but at first glance it does not seem to be programmed in python itself / does not have the described problems ..

I found all previous solutions I have seen to complicated or too fragile, which is why I have always oriented myself to my shell scripts ... "bash" .. somewhat archaic but it always works. With rye we could have a real alternative in our hands ... we should definitely pursue this further ..

And it's also from Armin Ronacher ... then it can only be good :)

Looks promising .. Most python build, env and package tools are based on the python itself installed on a system ... since different python versions are installed on all systems this usually does not work well (e.g. pyenv).

It uses prebuilt python version from https://github.com/indygreg/python-build-standalone
See https://gregoryszorc.com/docs/python-build-standalone/main/

I still have to take a closer look at Rye, but at first glance it does not seem to be programmed in python itself / does not have the described problems ..

It is written in Rust and some Python: the first thing rye does is to download a Python version for its Python scripts. This is seamless, just a line of code.

I found all previous solutions I have seen to complicated or too fragile

The tool is new and hacky according Armin (I'm not sure he uses exactly this word, but that's the idea), but it gets good comments and reviews. The fact that astral endorse the project is another good point.

This means that everybody willing to work on SearXNG needs to install rye, right? Due to the fact that rye is not really a standard package and probably not part of many Linux repositories, I personally am not sure about this PR.

Manually installing such a package before contributing is possible has the downside that some contributors might fail setting things up properly, and also cause inconvenience? (just my opinion)

This means that everybody willing to work on SearXNG needs to install rye, right?

Yes

Due to the fact that rye is not really a standard package and probably not part of many Linux repositories, I personally am not sure about this PR.

There is an issue about that: astral-sh/rye#452

Also, SearXNG already has many unusual setup:

• nvm is downloaded directly from GitHub.
• go built chain was downloaded directly from golang.org
• redis source coded is downloaded and then compiled outside of any package management.

Manually installing such a package before contributing is possible has the downside that some contributors might fail setting things up properly, and also cause inconvenience?

I have not checked, may be it is possible to install it inside the ./local directory, so rye would be installed like other tools. In this case, would it be a problem?

I have not checked, may be it is possible to install it inside the ./local directory, so rye would be installed like other tools. In this case, would it be a problem?

That sounds great 👍

Installation without user interaction in a custom directory:

1/ Download the binary from https://github.com/astral-sh/rye/releases/tag/

2/ Run

$ RYE_HOME="$(pwd)/local" rye self install --toolchain /usr/bin/python3.10 --no-modify-path --yes

-->

Welcome to Rye!

This installer will install rye to /home/aflament/code/searxng/local
This path can be changed by exporting the RYE_HOME environment variable.

Details:
  Rye Version: 0.27.0
  Platform: linux (x86_64)
  Internal Toolchain Path: /usr/bin/python3.10

Installed binary to /home/aflament/code/searxng/local/shims/rye
Registering toolchain at /usr/bin/python3.10
Registered toolchain as cpython@3.10.12
Bootstrapping rye internals
Found a compatible Python version: cpython@3.10.12
Updated self-python installation at /home/aflament/code/searxng/local/self
Skipping PATH modification. You will need to add /home/aflament/code/searxng/local/shims to your PATH manually.

All done!

As described in the log, the PATH must contains local/shims, and it is all set.

I will try to add that to the PR, so rye won't be a prior requirement.

Done: rye is automatically downloaded and installed in the .local directory.

Actually now, you don't even need Python: rye is going to download the version defined in .python-version (It is possible to ask rye to use /usr/bin/python3 with rye toolchain register ).