Cross-platform Python environment management.
Project description
cpenv
Cross-platform Python environment management.
Installation
pip install cpenv
Environment Variables
$CPENV_HOME - Path where environments will be created (default: ~/.cpenv)
$CPENV_ACTIVE - Path to active environment
$CPENV_APP - Path to active app module
Create
cpenv create test
Create an environment named test.
Activate
cpenv activate test
All activated environments are stored in a cache in ~/.cpenv/envcache.yml. First environments are looked up by name in CPENV_HOME path, then looked up in envcache.yml. This means you can store and activate environments by name regardless of where they are stored on the file system, so long as you activate them once by full path. The paths stored in the cache are validated each time you run cpenv.
Deactivate
Each environment runs in a subshell so deactivation is handled through the shell command exit.
Application Modules
Application modules are sub environments used to configure DCC applications like Autodesk Maya and The Foundry’s Nuke. You can find two examples of app modules at http://github.com/cpenv/maya_module.git and http://github.com/cpenv/nuke_module.git. Each app module includes an appmodules.yml file with a command to launch the application, environment variables, and any python dependencies the module requires.
Create an app module
cpenv create --module maya2016 https://github.com/cpenv/maya_module.git
Adds the default maya module to the active environment test. All app modules are installed to $CPENV_ACTIVE/appmodules.
Launch an app module
cpenv launch maya2016
Launches maya2016 app module using the command and arguments provided in the appmodule.yml file.
Remove an app module
cpenv remove --module maya2016
Deletes the app module.
Removing Environments
cpenv remove test
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.