-
Notifications
You must be signed in to change notification settings - Fork 2
Allow to keep setup command in venv #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
base: main
Are you sure you want to change the base?
Allow to keep setup command in venv #56
Conversation
…tracting OLD_* paths
…setup-command Allow to keep setup command in venv
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexanderHeidelbach I don't think this is working as expected. Can you give me a minimum reproducer of how you're trying to use this to setup an environment on CVMFS with this?
EOT | ||
) | ||
_SET_PYTHONPATH+=$'\n' | ||
if [ "${_keep_setup}" = true ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So maybe what we could do is guard this a bit so that before using _keep_setup
we check to see if _setup_command
is set and if not error out as the intended use case here is to use --setup <some setup command> --keep-setup
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would check for the correct usage directly in the beginning such that the venv
is not even created if the intended use case is not met.
Added option to allow the injection of the setup command of the cvmfs environment to the
activate
script of the createdvenv
. This allows the user to automatically set up the cvmfs environment when reactivating thevenv
.