Closed vladimir-v-diaz closed 7 years ago
Definitely a good move!
I'd change this slightly: since the requirements are currently in setup.py, we should:
Shouldn't the dependencies still be listed in setup.py? For example, someone might only have access to the source distribution and not the GitHub repository. It is my understanding that dev-requirements.txt is usually meant for developers working on the codebase to ensure everyone is using the same set of installed dependencies. requirements.txt files also come in handy with CI tools like Travis.
We could leave them in there, but if they're in there and the "-e ." line is early in dev-requirements.txt, then that means that the versions specified in setup.py will be the ones actually installed. When pip sees the new version constraints a few moments later, it will probably ignore them.
You could just move the "-e ." line to the end of the dev-requirements.txt file.
Okay, I reordered the dependencies listed in dev-requirements.txt
Add a requirements.txt file for pip that pins specific versions of dependencies. The README is updated to include the pip command that uses dev-requirements.txt