Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend pymultihash instead of the defunct python-multihash #102

Merged
merged 1 commit into from
Sep 28, 2018

Conversation

ntninja
Copy link
Contributor

@ntninja ntninja commented Sep 28, 2018

The repo of the currently recommend multihash implementation doesn't even exist anymore. @ivilata's implementation of multihash on-the-other hand is quite feature-complete, comes with good documentation and was positively received by previous py-ipfs developers. The heavy-lifting is done by Python's built-in hashlib module that python developers are already familiar with. Hence I believe this should become the recommended implementation for python. If @ivilata isn't opposed to it, I believe it should also be moved to the organization (as https://github.com/multiformats/py-multihash).

@Stebalien
Copy link
Member

Stebalien commented Sep 28, 2018

It has a few small issues (reported) but looks pretty good overall (and it still exists which is a huge plus...).

@Stebalien Stebalien merged commit b6421e2 into multiformats:master Sep 28, 2018
@Stebalien
Copy link
Member

Thanks!

@ntninja
Copy link
Contributor Author

ntninja commented Sep 28, 2018

What's your stance on moving it to the organization?

@ntninja ntninja deleted the patch-1 branch September 28, 2018 16:39
@Stebalien
Copy link
Member

@Alexander255 ideally, I'd like to have ivilata/pymultihash#5 and ivilata/pymultihash#7 fixed first so users don't run into any nasty incompatibilities. After that, I see no reason not to.

@diasdavid do we have a policy for onboarding libraries into our organizations?

@ivilata
Copy link
Contributor

ivilata commented Oct 2, 2018

Hey, it's an honor to read that this is now a recommended implementation! 😄

Regarding the two issues, I currently have no time to concentrate on them (this might get better in a couple of months), but pull requests are very welcome. I'd also be happy to delegate maintenance if need be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants