Introduction
‘’mk.recipe.pip’’ is a zc.buildout recipe which allow you to piggyback on pip to install certain packages that not possible to install using zc.recipe.egg. It does not replace zc.recipe.egg (not yet) but should be used in conjuction with that recipe. It’s based on ‘’collective.recipe.modwsgi’.’
It is very simple to use. This is a minimal ‘’buildout.cfg’’ file:
[buildout]
parts = pip base
[pip]
recipe = mk.recipe.pip
requirements =
svn+http://django-grappelli.googlecode.com/svn/trunk
disable-pth = true
[base]
recipe = zc.recipe.egg
interpreter = python
eggs =
grappelli
Django==1.5.1
Above, grappelli will be installed into eggs directory so that zc.recipe.egg can pick it up. This especially usefull to install private packages that only available maybe through svn or other version control system.
Changelogs
0.3 - 2013-05-08
Missing files in 0.2.
0.2 - 2013-05-08
Add eggs option, can be used in zc.recipe.egg eggs’s options.
0.1
Initial release.
Metadata
Release files for mk.recipe.pip 0.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 |
|---|---|---|---|---|
| mk.recipe.pip-0.3.zip | 8.8 kB | Without provenance | Details for mk.recipe.pip-0.3.zip |
Release files / mk.recipe.pip-0.3.zip
| Download URL | mk.recipe.pip-0.3.zip |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
935eb9c695a1774e5989f624938ff0595536569bc62a3c9c02448e8c6649d5d9
|
|
BLAKE2b-256 checksum How to use checksums |
d447256e8bcc041d9e0196e05302eb455c999251f84e4e6183f745d85be763bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mk.recipe.pip 0.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.