This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author oconnor663
Recipients Zooko.Wilcox-O'Hearn, christian.heimes, corona10, jstasiak, kmaork, larry, oconnor663, xtreak
Date 2021-04-19.03:44:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618803855.39.0.520127653381.issue39298@roundup.psfhosted.org>
In-reply-to
Content
An update a year later: I have a proof-of-concept branch that adds BLAKE3 support to hashlib: https://github.com/oconnor663/cpython/tree/blake3. That branch is API compatible with the current master branch of https://github.com/oconnor663/blake3-py. Both that module and the upstream BLAKE3 repo are ready to be tagged 1.0, just waiting to see whether any integrations like this one end up requesting changes.

Would anyone be interested in moving ahead with this? One of the open questions would be whether CPython would vendor the BLAKE3 optimized assembly files, or whether we'd prefer to stick to C intrinsics.
History
Date User Action Args
2021-04-19 03:44:15oconnor663setrecipients: + oconnor663, larry, christian.heimes, Zooko.Wilcox-O'Hearn, jstasiak, corona10, xtreak, kmaork
2021-04-19 03:44:15oconnor663setmessageid: <1618803855.39.0.520127653381.issue39298@roundup.psfhosted.org>
2021-04-19 03:44:15oconnor663linkissue39298 messages
2021-04-19 03:44:15oconnor663create