buildout recipe to run python methods as hooks
Project description
Supported options
=================
hooks
Custom python script(s) and method(s) that will be executed.
The format of the options is::
/path/to/the/module.py:name_of_callable
where the first part is a filesystem path to the python module and
the second part is the name of the callable in the module that
will be called. The callable will be passed two parameters: the
``options`` dictionary from the recipe and the global ``buildout``
dictionary. The callable is not expected to return anything.
This code was essentially ripped out of plone.recipe.command_
and hexagonit.recipe.cmmi_
.. _plone.recipe.command : http://dev.plone.org/collective/browser/buildout/plone.recipe.command
.. _hexagonit.recipe.cmmi : http://pypi.python.org/pypi/hexagonit.recipe.cmmi
Example usage
=============
It can be helpful to define in [buildout] a::
hooks = ${buildout:directory}/hooks
then invoke like::
[your_part_section]
hooks = ${buildout:hooks}/hookfile.py:methodname
The value of 'hooks' can be a whitespace-separated list of
files:methods to specify multiple hooks that are executed in
order. You can also specify options that can be used in your
hooks. Example::
[your_part_section]
hooks = ${buildout:hooks}/hookfile1.py:methodname1
${buildout:hooks}/hookfile2.py:methodname2
${buildout:hooks}/hookfile2.py:methodname3
option1 = xyzzy
option2 = You won't get it up the stairs.
=================
hooks
Custom python script(s) and method(s) that will be executed.
The format of the options is::
/path/to/the/module.py:name_of_callable
where the first part is a filesystem path to the python module and
the second part is the name of the callable in the module that
will be called. The callable will be passed two parameters: the
``options`` dictionary from the recipe and the global ``buildout``
dictionary. The callable is not expected to return anything.
This code was essentially ripped out of plone.recipe.command_
and hexagonit.recipe.cmmi_
.. _plone.recipe.command : http://dev.plone.org/collective/browser/buildout/plone.recipe.command
.. _hexagonit.recipe.cmmi : http://pypi.python.org/pypi/hexagonit.recipe.cmmi
Example usage
=============
It can be helpful to define in [buildout] a::
hooks = ${buildout:directory}/hooks
then invoke like::
[your_part_section]
hooks = ${buildout:hooks}/hookfile.py:methodname
The value of 'hooks' can be a whitespace-separated list of
files:methods to specify multiple hooks that are executed in
order. You can also specify options that can be used in your
hooks. Example::
[your_part_section]
hooks = ${buildout:hooks}/hookfile1.py:methodname1
${buildout:hooks}/hookfile2.py:methodname2
${buildout:hooks}/hookfile2.py:methodname3
option1 = xyzzy
option2 = You won't get it up the stairs.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Close
Hashes for koansys.recipe.hooks-0.1-dev-r7.tar.gz
Algorithm | Hash digest | |
---|---|---|
SHA256 | aa437a66f6635a2886adb05da1b837c851d8056f8aeb3f900646c1b49a2bccf8 |
|
MD5 | 73a90696db17b08d92bd3e7b88b99d76 |
|
BLAKE2b-256 | 94c3d0f12cdc0824f6ba7c0c1d52678a0382bdf194b93f46eac6e50264643378 |