On 04/01/2015 04:26 PM, Adam Spiers wrote:
Jason Craig <os-dev@jacraig.com> wrote:
Packages declare their dependencies in setup.py, so that is where py2pack looks for them, just like setuptools and pip.
But setup.py is just code, so it can invoke code in other files in order to determine the dependencies.
Is that a problem?
As far as I understand it, a requirements file is more for developing a set of packages with versions known to work well in a certain configuration--e.g. if you are deploying a web application with a complex list of requirements that is only really tested with a specific set of versions of those requirements, something of that nature.
I think this behavior is by design.
If so, IMHO this design is broken because it excludes the pbr approach, and the OpenStack community is a significant contributor to the Python ecosystem:
Maybe the pbr approach is broken. I am rather fond of this post https://caremad.io/2013/07/setup-vs-requirement/ which explains why requirements.txt perhaps should be used differently than setup.py. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org