From c2441d5629fc5491bac597da8d975dd1b85a5ade Mon Sep 17 00:00:00 2001 From: zooko <> Date: Fri, 21 Sep 2007 13:45:32 +0000 Subject: [PATCH] update about how we now use setuptools [Imported from Trac: page Packaging, version 11] --- Packaging.md | 20 ++++---------------- 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/Packaging.md b/Packaging.md index 5c1b263..2ea7f53 100644 --- a/Packaging.md +++ b/Packaging.md @@ -43,9 +43,9 @@ For libraries that Tahoe uses, we have these desiderata: ## setuptools -One option is to use a Python packaging tool named [setuptools](http://cheeseshop.python.org/pypi/setuptools). +We use a Python packaging tool named [setuptools](http://cheeseshop.python.org/pypi/setuptools). -Advantages (note that each of these are options provided by setuptools, not requirements imposed by the use of setuptools): +Advantages: * management of dependencies (even on platforms that don't have a native package manager); This is the important feature. @@ -53,18 +53,6 @@ Advantages (note that each of these are options provided by setuptools, not requ * for hackers who want to use Tahoe, and who like setuptools, this makes using Tahoe convenient and pleasant for them - * replace "build/configure/package/distribute/test/develop" code written in the Make language with code written in Python; One specific instance of this is `./setup.py test` which runs the unit tests +Possible advantages: -We already have [a patch](http://allmydata.org/darcs.cgi/tahoe-setuptools/?c=annotate&p=20070522155758-eb44e-15f8219675d4b35b2488bc742f46714526d61cb3.gz) which changes Tahoe to use setuptools, but it doesn't solve the "How to integrate smoothly with platform-specific package managers." part yet. - -## related tickets - -The primary ticket for tracking our progress on this issue: - -#82 -- remove the "build" step in the "edit, build, run" cycle - -Other related tickets: - -#10 -- clean up after yourself when told to "make clean" - -#47 -- use pyutil as a separate package and contribute src/allmydata/util/* into pyutil + * perhaps in the future we will replace "build/configure/package/distribute/test/develop" code written in the Make language with code written in Python; One specific instance of this is `./setup.py test` which runs the unit tests