path: root/python/pysetuptools/README
diff options
author Robby Workman <>2011-03-16 01:13:49 -0500
committer Robby Workman <>2011-03-20 12:33:01 -0500
commit7a1b4848a3d34a263544fadf08178c91c12fbad0 (patch)
tree8987d0fc908e371dfa87445425f59c7514075b37 /python/pysetuptools/README
parent987d45e99a299c3b24418b2976e8ec9d5f3bf404 (diff)
python/*: Moved a lot of Python stuff here
The criteria for whether something "belongs" in Development or Libraries or Python or ... is admittedly arbitrary. As a general rule, if it could be either Libraries or Python, it's Python. Otherwise, pick one and we'll go from there... Signed-off-by: Robby Workman <>
Diffstat (limited to 'python/pysetuptools/README')
1 files changed, 18 insertions, 0 deletions
diff --git a/python/pysetuptools/README b/python/pysetuptools/README
new file mode 100644
index 0000000000..851e044f23
--- /dev/null
+++ b/python/pysetuptools/README
@@ -0,0 +1,18 @@
+pysetuptools (a collection of enhancements to Python distutils)
+Note: the name of the source package is 'setuptools'. Since 'setuptools'
+is such a generic name, this package uses the name 'pysetuptools' to avoid
+any potential future conflicts. The actual installation paths and file
+names are not modified in any way.
+setuptools allow you to more easily build and distribute Python packages,
+especially ones that have dependencies on other packages.
+Packages built and distributed using setuptools look to the user like ordinary
+Python packages based on the distutils. Your users don't need to install or
+even know about setuptools in order to use them, and you don't have to include
+the entire setuptools package in your distributions. By including just a single
+bootstrap module (an 8K .py file), your package will automatically download and
+install setuptools if the user is building your package from source and doesn't
+have a suitable version already installed.
+Requires: >=python-2.3.5 on 32-bit systems >=python-2.4 on 64-bit systems