Commit 4e61cb51 authored by Jim Fulton's avatar Jim Fulton

Renamed the runsetup command to setup.

parent 90eefec9
...@@ -22,6 +22,14 @@ priorities include: ...@@ -22,6 +22,14 @@ priorities include:
Change History Change History
************** **************
Next Release
============
Feature Changes
---------------
Renamed the runsetup command to setup. (The old name still works.)
1.0.0b9 (2006-10-02) 1.0.0b9 (2006-10-02)
==================== ====================
......
...@@ -619,7 +619,7 @@ class Buildout(dict): ...@@ -619,7 +619,7 @@ class Buildout(dict):
for ep in pkg_resources.iter_entry_points('zc.buildout.extension'): for ep in pkg_resources.iter_entry_points('zc.buildout.extension'):
ep.load()(self) ep.load()(self)
def runsetup(self, args): def setup(self, args):
setup = args.pop(0) setup = args.pop(0)
if os.path.isdir(setup): if os.path.isdir(setup):
setup = os.path.join(setup, 'setup.py') setup = os.path.join(setup, 'setup.py')
...@@ -646,6 +646,8 @@ class Buildout(dict): ...@@ -646,6 +646,8 @@ class Buildout(dict):
finally: finally:
os.close(fd) os.close(fd)
os.remove(tsetup) os.remove(tsetup)
runsetup = setup # backward compat
runsetup_template = """ runsetup_template = """
import sys import sys
...@@ -879,7 +881,7 @@ def main(args=None): ...@@ -879,7 +881,7 @@ def main(args=None):
if args: if args:
command = args.pop(0) command = args.pop(0)
if command not in ('install', 'bootstrap', 'runsetup'): if command not in ('install', 'bootstrap', 'runsetup', 'setup'):
_error('invalid command:', command) _error('invalid command:', command)
else: else:
command = 'install' command = 'install'
......
...@@ -9,7 +9,7 @@ package index. If your script uses setuptools, you'll need setuptools ...@@ -9,7 +9,7 @@ package index. If your script uses setuptools, you'll need setuptools
in your Python path, which may be an issue if you haven't installed in your Python path, which may be an issue if you haven't installed
setuptools into your Python installation. setuptools into your Python installation.
The buildout runsetup command is helpful in a situation like this. It The buildout setup command is helpful in a situation like this. It
can be used to run a setup script and it does so with the setuptools can be used to run a setup script and it does so with the setuptools
egg in the Python path and with setuptools already imported. The fact egg in the Python path and with setuptools already imported. The fact
that setuptools is imported means that you can use setuptools-based that setuptools is imported means that you can use setuptools-based
...@@ -35,7 +35,7 @@ We can use the buildout command to generate the hello egg: ...@@ -35,7 +35,7 @@ We can use the buildout command to generate the hello egg:
>>> cd(sample_buildout) >>> cd(sample_buildout)
>>> import os >>> import os
>>> print system(os.path.join('bin', 'buildout') >>> print system(os.path.join('bin', 'buildout')
... +' runsetup hello -q bdist_egg'), ... +' setup hello -q bdist_egg'),
buildout: Running setup script hello/setup.py buildout: Running setup script hello/setup.py
zip_safe flag not set; analyzing archive contents... zip_safe flag not set; analyzing archive contents...
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment