Am 14.02.2015 um 00:11 schrieb Donald Stufft: ... > requirements.txt and setup.py serve different purposes, requirements.txt is > for > an environment, setup.py is for a package. It doesn't make sense for a > setup.py > to read from a requirement.txt just like it wouldn't make sense for a deb > package to read from a Chef cookbook. > > Often the reason people do this is they want to support people installing > their > thing with ``pip install -r requirements.txt`` from within a check out without > needing to list their dependencies twice. That's a reasonable thing to want > which is why the requirements file format has a construct that enables it, > simply make a requirements.txt file that contains "." or "-e ." and pip will > automatically install the project and all of it's dependencies. > > For more information, see https://caremad.io/2013/07/setup-vs-requirement/.
thank you very much for your answer. I understand the topic better. The comparison to a chef cookbook was good. -- http://www.thomas-guettler.de/ _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
