Repository navigation
Ensuring no foot-guns: pipx install via pip / conda
#1253
Replies: 1 comment
|
That symlink arrangement can work without activating I checked the same arrangement with a real micromamba environment containing Python 3.11.17 and pipx 1.17.12. With that environment inactive, the symlinked The part to keep stable is the environment behind those links:
You can check which launcher your shell finds with: command -v pipx
pipx --versionThis matches the pipx environment and launcher model. Python’s virtual environment documentation also explains why absolute interpreter paths make moving an existing environment unreliable. |
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!
All reactions