I’m curently packaging a python 3.10 application including a anaconda virtual env.
The app can (can and must) be called by any user without the need to modify their .bashrc file or anything else in their home dir
Till using conda from a python 3.10 dist it was possible to enable the venv using the old way by sourcing an
/path/to/python_venv/bin/activate file using a wrapper script which then called the python binary with the application script as parameter.
Newer Versions of conda environments (from anaconda distribution) require this weird conda init stuff in .bashrc which does some magic things I don’t understand.
Of course I could do a conda init on a reference machine and move the generated stuff to my wrapper script but I’d like to know if there’s a minimal command set to place here, since this is called every time may app get’s called.
What can I put in my wrapper script to activate the venv, instaed of the old source command
without doing magic things like changing promt and whatever ist does elsewhere ?
jb0815 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.