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