-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Source common_startup script vs running it so the activated venv appl… #1899
Source common_startup script vs running it so the activated venv appl… #1899
Conversation
…ies to the parent script's shell. Fixes galaxyproject#1847.
This is an alternate fix to #1890. I don't know the background of why the common startup scripts were executed and not sourced, maybe someone who has tinkered with this can chime in? (on the face of it, this seems to be a better approach to me) |
Ping @natefoo, he expressed some reservations on IRC when we spoke about this option. |
@galaxybot test this |
👍 - we really need to merge one of these fixes - I don't care which. |
We just need to take care that nothing in Ideally, the venv creation code should probably be placed in a function and the variables it uses should be set It should also remain possible to call |
…ies to the parent script's shell. Fixes #1847.
My testing resulted in the venv getting and staying activated when starting reports app.