On Wed, Mar 24, 2010 at 12:50 PM, Darren Dale <dsdale24@gmail.com> wrote:
On Wed, Mar 24, 2010 at 6:26 AM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
The open question is: do we want to include a full installer that takes care of installing / removing dependencies as well ?
I think not. Pip already provides this feature on the top of distutils (and distutils2 later I guess) and is not hard to install on the top of Python.
Is pip able to determine and install dependencies recursively, like easy_install does? Or is it up to the requested package to it specify its dependencies (and its dependencies dependencies) in a pip requirements file that is distributed separately?
Pip uses the same standard: the install_requires option in setuptools, that is put in a requires.txt file when the egg-info is computed. Notice that we have defined this field in the new version of the metadata (PEP 345) for future interoperability. Let's remove python-dev for packaging talks in the next answers Regards Tarek
Darren
-- Tarek Ziadé | http://ziade.org