mozilla/funfactory — comment on commit 4884c0b7e9fd5d7db920a28f6c4d0b233c336253
File:  line 0
By fwenzel:

I understand the sentiment against requirements.txt, but consider the following:

* vendor/ is really only a build artifact, it's a snapshot of what requirements.txt represents.
* vendor/ makes it hard to know what exactly is installed, *unless* all requirements are git submodules. If you pip install packages into vendor/lib, it becomes more than only a little bit annoying to tell what exact requirements the project at hand has.

That's why I actually like requirements.txt because it's a somewhat human-readable version of what the devs *intended* the requirements of this project to be, not what months upon months of iterative evolution of the vendor/ directory happened to result in. To put it more bluntly: If someone (including me) f's up vendor/, I should be able to throw it away and rebuild it, just by looking at requirements.txt.