{ "info": { "author": "Jim Fulton", "author_email": "jim@zope.com", "bugtrack_url": null, "classifiers": [ "Development Status :: 5 - Production/Stable", "Framework :: Buildout", "Intended Audience :: Developers", "License :: OSI Approved :: Zope Public License", "Programming Language :: Python", "Programming Language :: Python :: 2", "Programming Language :: Python :: 2.6", "Programming Language :: Python :: 2.7", "Programming Language :: Python :: 3", "Programming Language :: Python :: 3.2", "Programming Language :: Python :: 3.3", "Topic :: Software Development :: Build Tools", "Topic :: Software Development :: Libraries :: Python Modules" ], "description": "********************************\nBuildout Egg-Installation Recipe\n********************************\n\n.. contents::\n\nThe egg-installation recipe installs eggs into a buildout eggs\ndirectory. It also generates scripts in a buildout bin directory with \negg paths baked into them.\n\n\nChange History\n**************\n\n2.0.7 (2018-07-02)\n==================\n\n- For the 2.0.6 change, we require zc.buildout 2.12.0. The `install_requires`\n in `setup.py` now also says that.\n\n\n2.0.6 (2018-07-02)\n==================\n\n- Added extra keyword argument ``allow_unknown_extras`` to support zc.buildout\n 2.12.0.\n\n\n2.0.5 (2017-12-04)\n==================\n\n- Fixed #429: added sorting of working set by priority of different\n type of paths (develop-eggs-directory, eggs-directory, other paths).\n\n\n2.0.4 (2017-08-17)\n==================\n\n- Fixed #153: buildout should cache working set environments\n [rafaelbco]\n\n\n2.0.3 (2015-10-02)\n==================\n\n- Releasing zc.recipe.egg as a wheel in addition to only an sdist. No\n functional changes.\n [reinout]\n\n2.0.2 (2015-07-01)\n==================\n\n- Fixed: In ``zc.recipe.egg#custom`` recipe's ``rpath`` support, don't\n assume path elements are buildout-relative if they start with one of the\n \"special\" tokens (e.g., ``$ORIGIN``). See:\n https://github.com/buildout/buildout/issues/225.\n [tseaver]\n\n2.0.1 (2013-09-05)\n==================\n\n- Accomodated ``zc.buildout`` switch to post-merge ``setuptools``.\n\n2.0.0 (2013-04-02)\n==================\n\n- Enabled 'prefer-final' option by default.\n\n2.0.0a3 (2012-11-19)\n====================\n\n- Added support for Python 3.2 / 3.3.\n\n- Added 'MANIFEST.in'.\n\n- Support non-entry-point-based scripts.\n\n- Honor exit codes from scripts (https://bugs.launchpad.net/bugs/697913).\n\n2.0.0a2 (2012-05-03)\n====================\n\n- Always unzip installed eggs.\n\n- Switched from using 'setuptools' to 'distribute'.\n\n- Removed multi-python support.\n\n1.3.2 (2010-08-23)\n==================\n\n- Bugfix for the change introduced in 1.3.1.\n\n1.3.1 (2010-08-23)\n==================\n\n- Support recipes that are using zc.recipe.egg by passing in a dict, rather\n than a zc.buildout.buildout.Options object as was expected/tested.\n\n1.3.0 (2010-08-23)\n==================\n\n- Small further refactorings past 1.2.3b1 to be compatible with\n zc.buildout 1.5.0.\n\n1.2.3b1 (2010-04-29)\n====================\n\n- Refactored to be used with z3c.recipe.scripts and zc.buildout 1.5.0.\n No new user-visible features.\n\n1.2.2 (2009-03-18)\n==================\n\n- Fixed a dependency information. zc.buildout >1.2.0 is required.\n\n1.2.1 (2009-03-18)\n==================\n\n- Refactored generation of relative egg paths to generate simpler code.\n\n1.2.0 (2009-03-17)\n==================\n\n- Added the `dependent-scripts` option. When set to `true`, scripts will\n be generated for all required eggs in addition to the eggs named\n specifically. This idea came from two forks of this recipe,\n `repoze.recipe.egg` and `pylons_sandbox`, but the option name is\n spelled with a dash instead of underscore and it defaults to `false`.\n\n- Added a relative-paths option. When true, egg paths in scripts are generated\n relative to the script names.\n\n1.1.0 (2008-07-19)\n==================\n\n- Refactored to work honor the new buildout-level unzip option.\n\n\n1.1.0b1 (2008-06-27)\n====================\n\n- Added `environment` option to custom extension building options.\n\n1.0.0 (2007-11-03)\n==================\n\n- No code changes from last beta, just some small package meta-data\n improvements.\n\n1.0.0b5 (2007-02-08)\n====================\n\nFeature Changes\n---------------\n\n- Added support for the buildout newest option.\n\n1.0.0b4 (2007-01-17)\n====================\n\nFeature Changes\n---------------\n\n- Added initialization and arguments options to the scripts recipe.\n\n- Added an eggs recipe that *just* installs eggs.\n\n- Advertized the scripts recipe for creating scripts.\n\n1.0.0b3 (2006-12-04)\n====================\n\nFeature Changes\n---------------\n\n- Added a develop recipe for creating develop eggs.\n\n This is useful to:\n\n - Specify custom extension building options,\n\n - Specify a version of Python to use, and to\n\n - Cause develop eggs to be created after other parts.\n\n- The develop and build recipes now return the paths created, so that\n created eggs or egg links are removed when a part is removed (or\n changed).\n\n\n1.0.0b2 (2006-10-16)\n====================\n\nUpdated to work with (not get a warning from) zc.buildout 1.0.0b10.\n\n1.0.0b1\n=======\n\nUpdated to work with zc.buildout 1.0.0b3.\n\n1.0.0a3\n=======\n\n- Extra path elements to be included in generated scripts can now be\n set via the extra-paths option.\n\n- No longer implicitly generate \"py\\_\" scripts for each egg. There is\n now an interpreter option to generate a script that, when run\n without arguments, launches the Python interactive interpreter with\n the path set based on a parts eggs and extra paths. If this script\n is run with the name of a Python script and arguments, then the\n given script is run with the path set.\n\n- You can now specify explicit entry points. This is useful for use\n with packages that don't declare their own entry points.\n\n- Added Windows support.\n\n- Now-longer implicitly generate \"py\\_\" scripts for each egg. You can\n now generate a script for launching a Python interpreter or for\n running scripts based on the eggs defined for an egg part.\n\n- You can now specify custom entry points for packages that don't\n declare their entry points.\n\n- You can now specify extra-paths to be included in generated scripts.\n\n\n1.0.0a2\n=======\n\nAdded a custom recipe for building custom eggs using custom distutils\nbuild_ext arguments.\n\n1.0.0a1\n=======\n\nInitial public version\n\nDetailed Documentation\n**********************\n\nInstallation of distributions as eggs\n=====================================\n\nThe zc.recipe.egg:eggs recipe can be used to install various types if\ndistutils distributions as eggs. It takes a number of options:\n\neggs\n A list of eggs to install given as one or more setuptools\n requirement strings. Each string must be given on a separate\n line.\n\nfind-links\n A list of URLs, files, or directories to search for distributions.\n\nindex\n The URL of an index server, or almost any other valid URL. :)\n\n If not specified, the Python Package Index,\n http://cheeseshop.python.org/pypi, is used. You can specify an\n alternate index with this option. If you use the links option and\n if the links point to the needed distributions, then the index can\n be anything and will be largely ignored. In the examples, here,\n we'll just point to an empty directory on our link server. This\n will make our examples run a little bit faster.\n\nWe have a link server that has a number of distributions:\n\n >>> print_(get(link_server), end='')\n
\n bigdemo-0.1-py2.3.egg