<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div><div><br></div><div>Thus I expected naively that pip install . and python setup.py install should have the same results. <br></div></div></div></div></blockquote><div><br></div><div style>they process install_requires with different code, so things could turn out differently. </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div></div>
I have a reproducible case when the dependency handling differs if you use pip install -r requirements.txt or when you use python setup.py install <br><a href="https://github.com/zeromq/pyzmq/issues/414#issuecomment-24679800" target="_blank">https://github.com/zeromq/pyzmq/issues/414#issuecomment-24679800</a></div>
</div></div></blockquote><div><br></div><div style>I looked at this case, but atleast for me, the results were the same in all 3 cases</div><div style>(note that this project splits requirements.txt to generate 'install_requires')</div>
<div style>1) python setup.py install</div><div style>2) pip install . </div><div style>3) pip install -r requirements.txt</div><div style><br></div><div style>from "pip list" after the installs:</div><div style>
<div>anyjson (0.3.3)</div><div>configparser (3.3.0r2)</div><div>coverage (3.6)</div><div>docutils (0.11)</div><div>Jinja2 (2.7.1)</div><div>MarkupSafe (0.18)</div><div>picomongo (0.6)</div><div>Pygments (1.6)</div><div>pymongo (2.6.2)</div>
<div>pyzmq (13.1.0)</div><div>satlive (0.8.0)</div><div>Sphinx (1.2b2)</div></div><div><br></div><div style>btw, pip<1.4 has a bug where a stale build directory can lead to unexpected results.</div><div style>check for the offending project in <venv>/build (if using a virtualenv), or if using a global python /tmp/pip-build-<username></div>
<div><br></div><div><br></div></div></div></div>