This recipe generates activation script for zc.buildout environment.
This recipe can be used to create an activation script for zc.buildout environment.
You can see an example of how to use the recipe below:
>>> data = """ ... [buildout] ... parts = activate ... ... [activate] ... recipe = evg.recipe.activate ... """ >>> touch('buildout.cfg', data=data) >>> sh('bin/buildout -vvvvvv install activate')
Run buildout. Then on POSIX systems you can do:
$ source bin/activate
This will change your $PATH to point to the virtualenv bin/ directory. You have to use source because it changes the environment in-place. After activating an environment you can use the function deactivate to undo the changes:
(buildout) $ deactivate
The activate script will also modify your shell prompt to indicate which environment is currently active.
The recipe supports the following options:
- The name of the script created in the bin folder. This script is the equivalent of the activate virtualenv. It defaults to activate.
- The name of the function to deactivate environment. It defaults to deactivate.
- The name of the environment. It will use buildout directory name by default.
- The name of paltform to generate scripts. It will be detected by default. Possible values are: posix, win32, cygwin and jython.
- Fix Win32 bug, thanks to http://github.com/ochriste
- Added the name option to set prompt name.
- Added the platform option to select which kind of scripts will be generated.
- Added Windows support.
- Add CHANGES.txt to MANIFEST.in.
- Generate activation script for zc.buildout environment on POSIX systems.