On Wed, Mar 24, 2010 at 12:53 PM, Darren Dale <dsdale24@gmail.com> wrote:
On Wed, Mar 24, 2010 at 1:19 PM, Ian Bicking <ianb@colorstudy.com> wrote:
On Wed, Mar 24, 2010 at 7:27 AM, Olemis Lang <olemis@gmail.com> wrote:
My experience is that only `install_requires` is needed (unless you want to create app bundles AFAICR) , but in practice I've noticed that *some* easy_installable packages are not pip-able (though I had no time to figure out why :-/ )
Usually this is because Setuptools is poking at objects to do its work, while pip tries to work mostly with subprocesses. Though to complicate things a bit, pip makes sure the Setuptools monkeypatches to distutils are applied, so that it's always as though the setup.py says "from setuptools import setup". easy_install *also* does this.
But then easy_install starts calling methods and whatnot, while pip just does:
setup.py install --single-version-externally-managed --no-deps --record some_tmp_file
The --no-deps keeps Setuptools from resolving dependencies
Seeking clarification: how can pip recursively install dependencies *and* keep Setuptools from resolving dependencies?
Using the --no-deps option to setup.py