Fix dependency conflict for issue

#98 keep the consistency between setup.py and requirements.txt

Coverage remained the same at 94.723% when pulling 3d6e6c7084c2d06c3061346d734010d589ac4677 on NeolithEra:master into 80f3c1b4afd53a39b38be81ab6cedcf3ffb06496 on Netflix:master.

@russell-lewis BTW, dependency conflict problems are very common in practice in python ecosystem. I have encountered the issues several times. What's your oppinion on the challenges of detecting and repairing such issues? And how to avoid dependency conflict problems among python projects, especially for python library ecosystem?

This saves the day, the master branch is not working for me at the moment

Is it possible to merge this? Master is not working otherwise.

A workaround for this is pip install -r requirements.txt before any pip install -e .

I don't know if this project is still relevant/maintained but I wanted to tell you a little story about this guy that watched ~1hr video on youtube about how awesome Bless is, plus ~2hr wrapping his head around the idea of Certificate Authorities, because at this point he was oblivious about them, all he knows was private/public keys. Did I mention this guy doesn't have any background in Python? Anyways he continued removing blocker after blocker, almost there he thought then finally after deploying the solution ... he founds it's not working, Master branch is broken! You know where this is going right? Awesome project guys but the main function is broken and if I understand correctly the solution is right there on a PR from last year, so yeah what's up with that?

Install and builds were against pinned versions, which is why travis is still happy. See https://github.com/Netflix/bless#installation-instructions

I've given the list an update, but I've got to archive this project.