Package: tl.buildout_virtual_python
tl.buildout_virtual_pythonThis is azc.buildoutrecipe for setting up a virtual Python installation
inside a buildout. It is compatible with Python versions 2.5 through 2.7 andzc.buildoutversions 1.4 and upwards.The implementation makes use of thevirtualenvpackage, originally by Ian
Bicking.This recipe appears to be reliable, but the feature set is basically
determined by the author’s immediate needs. Don’t hesitate to send questions,
bug reports, suggestions, or patches to <thomas@thomas-lotze.de>.Use casesUsing a virtual Python gives you a Python environment which is writable for
other parts of the buildout without the need to compile Python from source. It
is isolated from other buildouts as well as from its parent Python
installation while it may still share the parent Python’s installed libraries.
Depending on your situation, these features may be considered helpful or
harmful. The recipe provides mechanism and leaves choosing policy up to you.Another aspect is that of providing a real Python executable which has access
to libraries installed by the buildout. Normally,zc.buildoutmakes
installed Python libraries accessible by creating the Python scripts inbin/as wrappers that set up an appropriatesys.pathand then call one
of theconsole_scriptentry points of some installed egg. Sometimes this
isn’t a workable approach, for example:when one of the programs callssys.executableand expects it to have
the same libraries installed that the calling code can importwhen the code being installed is intended to be run by an embedded Python
interpreter, such as when setting up amod_pythonapplicationIn those cases, install the required libraries into a virtual Python
environment and use that as another buildout part’s Python installation.OptionsA buildout part created by this recipe exports anexecutableoption so it
may be used as a part defining a Python installation in a buildout, i.e. a
buildout section’spythonoption may reference it.Configuration options:executable-name:Basename of the virtual Python installation’s interpreter executable.interpreter:Basename of a Python interpreter in the buildout’sbindirectory
that uses the virtual Python installation. No such interpreter is
created if the option is not set.real-python:Filesystem path to the interpreter executable of the Python
installation that should be used as the parent Python.site-packages:Boolean switch, whether to make the parent Python’ssite-packageslibrary directory available to the virtual Python.eggs:Specifications of eggs to be available to the virtual Python.extra-paths:Extra library paths to make available to the virtual Python.Exported options:location:Location of the buildout part containing the virtual Python
installation. This is the same as the virtual Python’ssys.prefix.executable:Filesystem path to the interpreter executable of the virtual Python
installation.About tl.buildout_virtual_pythonAuthor:Thomas Lotze<thomas@thomas-lotze.de>PyPI page:http://pypi.python.org/pypi/tl.buildout_virtual_python/Issue tracker:https://bitbucket.org/tlotze/tl.buildout_virtual_python/issues/Source code:https://bitbucket.org/tlotze/tl.buildout_virtual_python/Current change log:https://bitbucket.org/tlotze/tl.buildout_virtual_python/raw/tip/CHANGES.txtSupport the project: