-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Automatically run reshim? #37
Comments
Good question. This is clearly and issue for others as well. It could be in the docs at least. |
haha, I run into this question every time I get someone new to use asdf. It's definitely an issue, but because |
🤔 I suppose. But the same argument could be made for |
You’re probably just getting lucky. I’ve had issues with forgetting to reshim for every language I use asdf for; python, ruby, node, elixir, erlang, elm, etc. It’s inconsistent and I can’t explain what makes it work fine sometimes and poorly others, but certainly not isolated to python. I imagine virtualenvs switching their own shimming around probably contributes. |
This is the intended behavior, as I am not a big fan of doing things under the hood. |
When would the reshim happen? Is the feature request to wrap |
I know that other tools (e.g. gem for Ruby or npm for Node) offer post-installation hooks, which avoids the need for a wrapper. |
Wouldn't it be possible to just create an aliases that reshims after each install? e.g. |
This is actually quite similar to what pyenv is doing, for example: |
It looks like in master of asdf right now, there is some new support for auto reshimming. |
thank you @fozcodes for creating this issue, it works well for me for ruby, however, with python, I have to run reshim manually |
Hey guys,
I use ASDF for a lot of different langs, but in python anytime I install a new package via
pip
orpip3
I need to runasdf reshim python
to get it to load correctly.Is this intended behaviour? In other langs, e.g., JS, Elixir, Ruby, you don't need to do this.
Thanks!
The text was updated successfully, but these errors were encountered: