Ensuring no foot-guns: pipx install via pip / conda
#1253
Unanswered
pep-sanwer
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello-
As the title suggests, just wanting to make sure I'm not putting out a foot-gun for myself:
In an effort to separate my system python (on Ubuntu 22.04), I've previously had
pipxinstalled via apyenvvirtual env like:pyenv virtualenv 3.11.7 pipx_3.11.7pyenv shell pipx_3.11.7python -m pip install pipxpyenv global 3.11.7 pipx_3.11.7and using
pipxfrom thereRecently, I've consolidated my user python management to
micromambaand have reinstalledpipxlike:micromamba create -n pipx_env python=3.11 pipxln -s ~/.micromamba/envs/pipx_env/bin/pipx $LOCALBIN # i.e. ~/.local/binln -s ~/.micromamba/envs/pipx_env/bin//register-python-argcomplete $LOCALBINand using
pipxfrom thereQuite simply, I'm just wanting to ensure I am not setting myself for any wonky-ness down the line as a consequence of the above symlinks (it's a been of week of usage after the above, and I haven't encountered any issues so far)
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions