This package is a zc.buildout recipe which allow to install python packages using pip
Code repository: http://www.bitbucket.org/gawel/gprecipepip/
Report bugs at http://www.bitbucket.org/gawel/gprecipepip/issues/
Detailed Documentation
Supported options
The recipe supports the following options:
virtualenv
Virtualenv directory. The virtualenv is build in this directory (Default to parts/pip). You can also use an existing one. If a virtualenv option is found in the buildout section then this one is used except if the current section override it.
- env
extra environement vars used with subprocess
- indexes
Extra indexes url.
- install
A list of string passed to pip directly. A sub process is run per line. This allow to use –install-option.
- editables
A list of svn url. (svn+http://myrepo/svn/MyApp#egg=MyApp)
- eggs
A list of distribution to install with buildout
This recipe is based on zc.recipe.egg#scripts so options used by this recipe should also works.
Example usage
We’ll start by creating a buildout that uses the recipe:
>>> write('buildout.cfg',
... """
... [buildout]
... parts = test1
...
... [test1]
... recipe = gp.recipe.pip
... install =
... PasteScript
... interpreter = python
... scripts =
... paster = paster
... """)
Running the buildout gives us:
>>> print 'start', system(buildout) start... Installing test1. ... Generated script '/sample-buildout/bin/paster'. Generated interpreter '/sample-buildout/bin/python'...
Scripts are generated:
>>> ls('bin')
- buildout
- paster
- python
With the virtualenv binary as executable:
>>> print 'cat', cat('bin', 'paster')
cat .../parts/pip/bin/python
...
Complete Example
Here is a config file used to install Deliverance:
[buildout]
parts = eggs
download-cache = download
versions = versions
[versions]
# the recipe take care of versions
lxml=2.2alpha1
[eggs]
recipe = gp.recipe.pip
# needed to build static libs for lxml
env =
STATIC_DEPS=true
# packages to install with pip
install =
Cython
--install-option=--static-deps lxml
http://deliverance.openplans.org/dist/Deliverance-snapshot-latest.pybundle
# packages to install with buildout
eggs =
pyquery
# svn urls
editables =
svn+http://...
Contributors
Gael Pasgrimaud
Change history
0.5.3 (2012-9-5)
Remove -E from pip options [Aaditya Sood]
0.5.2 (2010-07-16)
Tagged [Gael Pasgrimaud]
0.5.1 (2009-12-14)
Support CFLAGS [Rob Miller]
0.5 (2009-12-8)
fix #1. bug with multi-index options. patch by Jannis Leidel.
use distribute
0.4 (2008-12-8)
allow to use extra env vars
fix bug with editables
allow to share virtualenvs / build_dir between buildouts
avoid duplicated installation by buildout
0.3 (2008-12-7)
Fixes: Always install a virtualenv. Split line arguments for install
0.2 (2008-12-7)
Fix error when no download cache is set [Gael Pasgrimaud].
Download
Metadata
Release files for gp.recipe.pip 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gp.recipe.pip-0.5.3.tar.gz | 7.4 kB | Without provenance | Details for gp.recipe.pip-0.5.3.tar.gz |
Release files / gp.recipe.pip-0.5.3.tar.gz
| Download URL | gp.recipe.pip-0.5.3.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f19258db6f24344e334159be7d4ed30f6378a398628e1f7f3c1e486b53ae4474
|
|
BLAKE2b-256 checksum How to use checksums |
02b967671f8f072dc72982a302790f36cb5cd96f120f2da5175b27df5946ac8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gp.recipe.pip 0.5.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.