(original) (raw)

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?