You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project that requires the PyPI cmake package during build. This creates a new shim ~/.pyenv/bin/cmake, which gets added to my PATH.
Problem is that when I'm not using the project, the ~/.pyenv/bin/cmake is still there. When I try to run $ cmake, I'm getting either an error that the correct Python version/environment is not active or it just uses the version from the shim.
Is this a bug/feature? How can I avoid this, aside from uninstalling all the conflicting packages?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a project that requires the PyPI
cmake
package during build. This creates a new shim~/.pyenv/bin/cmake
, which gets added to myPATH
.Problem is that when I'm not using the project, the
~/.pyenv/bin/cmake
is still there. When I try to run$ cmake
, I'm getting either an error that the correct Python version/environment is not active or it just uses the version from the shim.Is this a bug/feature? How can I avoid this, aside from uninstalling all the conflicting packages?
Beta Was this translation helpful? Give feedback.
All reactions