Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

Download
ActivePython
INSTALL>
pypm install z3c.recipe.runscript

How to install z3c.recipe.runscript

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install z3c.recipe.runscript
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
0.1.3 Available View build log
0.1.2 Available View build log
0.1.1 Available View build log
Windows (64-bit)
0.1.3 Available View build log
0.1.2 Available View build log
0.1.1 Available View build log
Mac OS X (10.5+)
0.1.3 Available View build log
0.1.2 Available View build log
0.1.1 Available View build log
Linux (32-bit)
0.1.3 Available View build log
0.1.2 Available View build log
0.1.1 Available View build log
Linux (64-bit)
0.1.3 Available View build log
0.1.2 Available View build log
0.1.1 Available View build log
 
License
ZPL 2.1
Dependencies
Lastest release
version 0.1.3 on Oct 8th, 2011

This run-script URL allows you to specify an arbitrary script to do the work of the recipe.

Detailed Documentation

The runscript Buildout Recipe

Some software packages are not easily installed using established build patterns, such as "configure, make, make install". In those cases you want to be able to use arbitrary scripts to build a particular part. This recipe provides a simple implementation to run a Python callable for each installing and updating a part.

>>> import os
>>> import z3c.recipe.runscript.tests
>>> scriptFilename = os.path.join(
...     os.path.dirname(z3c.recipe.runscript.tests.__file__), 'fooscripts.py')

Let's create a sample buildout to install it:

>>> write('buildout.cfg',
... """
... [buildout]
... parts = foo
...
... [foo]
... recipe = z3c.recipe.runscript
... install-script = %s:installFoo
... """ %scriptFilename)

The install-script option specifies the module and the function to call during the part installation. The function takes the local and buildout options as arguments. See tests/fooscripts.py for details.

When running buildout, the installFoo() function is called:

>>> print system('bin/buildout')
Installing foo.
Now executing ``installFoo()``

If we run the buildout again, the update method will be called, but since we did not specify any, nothing happens:

>>> print system('bin/buildout')
Updating foo.

Let's now specify the update script as well, causing the updateFoo() function to be called:

>>> write('buildout.cfg',
... """
... [buildout]
... parts = foo
...
... [foo]
... recipe = z3c.recipe.runscript
... install-script = %s:installFoo
... update-script = %s:updateFoo
... """ %(scriptFilename, scriptFilename))

But after a change like that, parts will be uninstalled and reinstalled:

>>> print system('bin/buildout')
Uninstalling foo.
Installing foo.
Now executing ``installFoo()``

Only now we can update the part:

>>> print system('bin/buildout')
Updating foo.
Now executing ``updateFoo()``

And that's it.

CHANGES
0.1.3 (2011-10-07)
  • Bug: fix Windows path support (containing semicolon such as 'c:\')
0.1.2 (2010-09-22)
  • Added test extra to declare test dependency on zope.testing.
  • Using Python's doctest module instead of depreacted zope.testing.doctest.
0.1.1 (2008-04-18)
  • Bug: Fix release to include CHANGES.txt.
0.1.0 (2007-07-30)
  • Initial Release.

Subscribe to package updates

Last updated Oct 8th, 2011

Download Stats

Last month:6

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.