Author: | Matt Wright |
---|
parameter | required | default | choices | comments |
---|---|---|---|---|
executable | no | The explicit executable or a pathname to the executable to be used to run easy_install for a specific version of Python installed in the system. For example easy_install-3.3 , if there are both Python 2.7 and 3.3 installations in the system and you want to run easy_install for the Python 3.3 installation. (added in Ansible 1.3) |
||
name | yes | A Python library name | ||
virtualenv | no | an optional virtualenv directory path to install into. If the virtualenv does not exist, it is created automatically | ||
virtualenv_command | no | virtualenv | The command to create the virtual environment with. For example pyvenv , virtualenv , virtualenv2 . (added in Ansible 1.1) |
|
virtualenv_site_packages | no | no |
|
Whether the virtual environment will inherit packages from the global site-packages directory. Note that if this setting is changed on an already existing virtual environment it will not have any effect, the environment must be deleted and newly created. (added in Ansible 1.1) |
Note
Requires virtualenv
# Examples from Ansible Playbooks
- easy_install: name=pip
# Install Bottle into the specified virtualenv.
- easy_install: name=bottle virtualenv=/webapps/myapp/venv
Note
Please note that the easy_install module can only install Python libraries. Thus this module is not able to remove libraries. It is generally recommended to use the pip module which you can first install using easy_install.
Note
Also note that virtualenv must be installed on the remote host if the virtualenv parameter is specified.