[mpdehaan2]

Ironically, the package to make your package requirements easier to write has additional requirements not in the core distribution :)

But more seriously, good idea in thinking that things should already be this way. The dual maintainance of the dependency list between setup.py and requirements.txt unfortunately leads to a lot of packages being left out of one or the other, or a package that works great from source that has a broken setup.py (which usually applies to everything I do).

A setup.py command for installing deps from setup.py would, to me, seem a bit more logical - but things already exist the way they do.

In the end though, it's a bit weird to deviate from the standard norms of package installation, at least in Python circles, which may introduce some confusion -- contrast this with Javascript circles that replace "the one true way" about every 3 months :)

[Socketubs]

Thank you for your feeback. Same reasons that encourage me to build `requirements` :)

I know this isn't perfect for now, `requirements` could evolve!