This buildout recipe allows you to reuse system wide eggs in your buildout. If SysEggs finds the requested eggs in you pythons site-packages directory (or PYTHONPATH) it will create a .egg-link to it. Other packages that require these eggs will not fetch them.
If force-sysegg is set to any value, the buildout will stop when any required sysegg is not installed.
Example
If you have an application that depends on the python image library (PIL) and you want to use the library that is already installed (e.g. with apt-get on Debian), you can use a buildout.cfg like this:
[buildout]
parts =
sysegg
otherpart
[sysegg]
recipe = osc.recipe.sysegg
force-sysegg =
eggs =
PIL
[otherpart]
recipe = zc.recipe.egg
egg = egg_that_depends_on_PIL
You should list sysegg before all other parts.
Changelog
- 0.1.2 (2010-03-25)
accept eggs definition to start with a blank line
add force-sysegg option. if set to any value, abort if any required egg is not installed
- 0.1.1 (2009-05-20)
use logging
fixed type in example
- 0.1 (2009-05-20)
initial release
1 maintainer
Metadata
1 maintainer
Release files for osc.recipe.sysegg 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| osc.recipe.sysegg-0.1.2.tar.gz | 2.7 kB | Details |
Release files / osc.recipe.sysegg-0.1.2.tar.gz
| Download URL | osc.recipe.sysegg-0.1.2.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aadfd50f1aa0918d2fb6b8a8683295d6261d3ce9a686df28f6b1049306b37adc
|
|
BLAKE2b-256 checksum How to use checksums |
ba0b636f5cc0d9c3b179f88110b036f364351b0fccd7e7742225897d05bcbd16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
