# Merkletools dependences pysha3

**URL:** <https://community.blockcerts.org/t/merkletools-dependences-pysha3/649>\
**Category:** Support\
**Created:** [December 22, 2017, 10:46am UTC](https://community.blockcerts.org/t/merkletools-dependences-pysha3/649 "2017-12-22T10:46:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [May 4, 2018, 4:43pm UTC](https://community.blockcerts.org/t/merkletools-dependences-pysha3/649/4 "2018-05-04T16:43:52Z")

</div>

@dannysuarez,

For the time being, try using the above approach. There’s some clashing going on with some dependencies, and the docker image seems to take care of it manually with this line:

`sed -i.bak s/==1\.0b1/\>=1\.0\.2/g /usr/lib/python3.*/site-packages/merkletools-1.0.2-py3.*.egg-info/requires.txt`

Alternatively, another approach is to manually update chainpoint’s dependency to 1.0.3. Unfortunately I do not know why it’s trying to use a previous version of merkeltools.

`vi /usr/local/lib/python3.6/site-packages/chainpoint-0.0.2.dist-info/METADATA`

Change to `merkletools (==1.0.2)` to `merkletools (>=1.0.3)`

---

_[View the full topic](https://community.blockcerts.org/t/merkletools-dependences-pysha3/649)._