[Plugin] Add a plugin for python3xxPackage.pip
#592
Merged
Conversation
This file contains hidden or 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
|
Did this really quick because I got annoyed with setting up |
mikeland73
approved these changes
Feb 7, 2023
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.
Summary
This plugin automatically sets up a virtual environment for python packages whenever a python3 version of
pipis added.VENV_DIRenvironment variable that determines where the virtualenv isvenvShellHook.shfile is added indevbox.dwhich creates the venv directory at $VENV_DIR if it doesn't already existvenvShellHook.shscriptI've left it so the user still needs to source the virtualenv manually, so they can choose whether or not to activate on starting devbox shell
How was it tested?
Tested in devbox-examples, create a simple requirements.txt and ran it with the plugin