Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use rtx instead of pyenv #1101

Open
astrojuanlu opened this issue May 23, 2023 · 1 comment
Open

Use rtx instead of pyenv #1101

astrojuanlu opened this issue May 23, 2023 · 1 comment

Comments

@astrojuanlu
Copy link

Is your feature request related to a problem? Please describe

I'm always frustrated with pyenv shims. See for example the conversation in pyenv/pyenv#1112

Describe the behaviour you'd like

A runtime selector that does not use shims.

Describe alternatives you've considered

https://github.com/jdxcode/rtx

No shims - shims cause problems, they break which, and add overhead. By default, rtx does not use them—however you can if you want to.
...
Unlike asdf which uses shim files to dynamically locate runtimes when they're called, rtx modifies PATH ahead of time so the runtimes are called directly. This is not only faster since it avoids any overhead, but it also makes it so commands like which node work as expected. This also means there isn't any need to run asdf reshim after installing new runtime binaries.

Additional context

@axonasif axonasif transferred this issue from gitpod-io/gitpod May 25, 2023
@mustard-mh
Copy link
Contributor

mustard-mh commented May 30, 2023

Hey @astrojuanlu , thank you for your suggestions 🙏.

At the moment, we don't have any immediate plans to change our default workspace images. Making such a change would impact all of our users. However, if you feel strongly about this, we encourage you to ask other users to upvote 👍 this issue. This will help bring more attention to the topic and potentially influence our future decisions.

In the meantime, if you wish, you can explore the option of configuring a workspace image yourself by following the instructions provided in our documentation.

Let us know if you have any further questions or concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants