Add ability to disable using a python venv to run whisk #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some scenarios it's undesirable to have a requirement on python virtual environments and using pip to download dependencies at on-demand, for instance when building in a restricted CI environment. This change let's users set the WHISK_NO_VENV shell variable to prevent the usage of python virtual environment and pip to install python dependencies required by whisk.py. The user must then make sure that these dependencies are available some other way, for instance by installing them via the system's native package manager.
|
I have a similar use case, because the host does not necessarily have the e.g python3.8-venv package installed (and the user is not necessarily able to install it). The workaround I did was to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some scenarios it's undesirable to have a requirement on python virtual environments and using pip to download dependencies at on-demand, for instance when building in a restricted CI environment.
This change let's users set the WHISK_NO_VENV shell variable to prevent the usage of python virtual environment and pip to install python dependencies required by whisk.py. The user must then make sure that these dependencies are available some other way, for instance by installing them via the system's native package manager.