Merkletools/pysha dependency conflict due to PyChainpoint

[ghost]

Because of the consistent issues popping up on the blockcerts forum over dependency conflicts (such as https://community.blockcerts.org/t/merkletools-pysha-dependency-conflict/1107), I've narrowed down the issue to PyChainpoint requiring a specific version of Merkletools that requires a specific pysha version that classes with other dependencies.

I've opened a ticket with PyChainpoint to use the latest version of Merkletools that would fix this dependency hell for us, but no response (lontivero/PyChainpoint#2)

We have a dockerfile script handle this for us automatically, but when people are running cert-issuer locally, across different environments, it's a pain to try to troubleshoot and deal with as a consumer.

I believe the only course of action to fix this dependency hell is to fork PyChainpoint and upload to pypi with a Requires.txt that has the latest version of Merkletools in it.

[guix77]

Meanwhile, for people not using Docker and using virtualenv, you can:

sed -i s/==1\.0b1/==1\.0\.2/g ./venv/lib/python3.5/site-packages/merkletools-1.0.2.dist-info/METADATA