Commit 7b3330d9 authored by Reinout van Rees's avatar Reinout van Rees

Updated documentation now that distutils-scripts are also supported

parent 0c93e5aa
......@@ -86,8 +86,8 @@ path. If you run it with a script and script arguments, the script
will run with the egg in its path. Of course, you can specify as many
eggs as you want in the eggs option.
If the egg provides any scripts (console_scripts entry points), those
will be installed in your bin directory too.
If the egg provides any scripts (console_scripts entry points or old-style
distutils scripts), those will be installed in your bin directory too.
Work on a package
=================
......
......@@ -861,9 +861,10 @@ Installing scripts
If any of the named eggs have ``console_script`` entry
points, then scripts will be generated for the entry points.
If a distribution doesn't use setuptools, it may not declare it's
entry points. In that case, you can specify entry points in the
recipe data.
If a distribution doesn't use setuptools, it may not declare it's entry
points. In that case, you can specify entry points in the recipe data.
Buildout *does attempt* to detect distutils-style scripts without an entry
point and will generate a script for them when found.
Script initialization
=====================
......
......@@ -945,6 +945,9 @@ sys.path like for the console_scripts:
<BLANKLINE>
print "distutils!"
Due to the nature of distutils scripts, buildout cannot pass arguments as
there's no specific method to pass them to.
Handling custom build options for extensions provided in source distributions
-----------------------------------------------------------------------------
......
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