<div dir="ltr"><div>Thanks for testing it and extra info!</div><div><br></div>It sounds like I 'fixed' the problem in the not-recommended way of including requirements.txt in the MANIFEST.in.<div><br></div><div>I've been using a pretty hefty setup.py: <a href="https://github.com/braingram/simple_setup">https://github.com/braingram/simple_setup</a> that attempts to auto-parse and detect 'everything' (finding packages, data, scripts, author info, version, requirements) with the hope of dropping it in a directory with a python module and magically having it pypi compatible. It sounds like it may be a pipe dream :)</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 28, 2014 at 2:41 PM, Marcus Smith <span dir="ltr"><<a href="mailto:qwcode@gmail.com" target="_blank">qwcode@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="">On Wed, Aug 27, 2014 at 2:51 PM, Brett Graham <span dir="ltr"><<a href="mailto:brettgraham@gmail.com" target="_blank">brettgraham@gmail.com</a>></span> wrote:<br>
<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">Hi,<div><br></div><div>I feel like these are stupid questions but I cannot seem to find a straight answer.</div>
<div><br></div><div>In brief,</div><div><div><br></div><div>1) what is egg-info/requires.txt used for?</div>
<div>2) how do I properly define requirements for pypi?</div></div><div><br></div><div>The details are:</div><div><br></div><div>I'm updating some packages on pypi and am having difficulty defining requirements.</div>
<div><br></div><div>One of the packages in question is: <a href="http://pypi.python.org/pypi/jsui" target="_blank">pypi.python.org/pypi/jsui</a></div><div><br></div><div>I'm initially defining the requirements in a requirements.txt that then gets parsed in setup.py and install_requires gets set to the contents of requirements.txt. Some of the output from python setup.py sdist build is below. The resulting requires.txt in jsui.egg-info is:</div>
<div><br></div><div>flask</div><div>wsrpc</div><div><br></div><div>However, when I upload this to pypi with "python setup.py sdist upload" I'm not seeing these requirements listed nor does pip installing the package install the requirements</div>
</div></blockquote><div><br></div></div><div>when I install jsui from pypi, it finds and installs flask and wsrpc.</div><div>what you've done is working.</div><div><br></div><div>in general though, I wouldn't parse "install_requires" from a requirements file.</div>
<div>It's mixing use cases.</div><div><br></div><div>see the "install_requires vs requirements files" section in the Python Packaging User Guide</div><div><a href="https://packaging.python.org/en/latest/technical.html#install-requires-vs-requirements-files" target="_blank">https://packaging.python.org/en/latest/technical.html#install-requires-vs-requirements-files</a><br>
</div><div><br></div><div><br></div></div></div></div>
</blockquote></div><br></div>