Releases: oconnor663/blake3-py
Releases · oconnor663/blake3-py
1.0.2_rerelease
Full Changelog: 1.0.2...1.0.2_rerelease
1.0.2
1.0.1
What's Changed
- Bump maturin, pyo3, add free-threaded 3.13t wheel by @ddelange in #47
- Bump gh-action-pypi-publish by @ddelange in #48
- Bump softprops/action-gh-release from 2.0.8 to 2.2.0 in the github-actions group by @dependabot in #49
- Fix windows 3.13t wheels by @ddelange in #50
New Contributors
- @dependabot made their first contribution in #49
Full Changelog: 1.0.0...1.0.1
1.0.0
Changes since 0.4.1:
- The public API hasn't changed for a long time, so the main purpose of this release is to "officially" stabilize it as-is.
- Prebuilt binaries are now published for more platforms, particularly AArch64. Thanks to @ddelange for implementing this.
blake3.pyi
(static typing stubs) now usescollections.abc.Buffer
for bytes-like arguments. This is more correct and more permissive, but it means that static typechecking requires Python 3.12+.
0.4.1
version 0.4.1
Changes since 0.4.0:
update
andupdate_mmap
now return self, so they can be called
fluently.
0.4.0
version 0.4.0
Changes since 0.3.4:
- Add blake3.update_mmap.
0.3.4
version 0.3.4
Changes since 0.3.3:
- Add type stubs. See blake3.pyi.
- Update PyO3 to v0.20.
0.3.3
version 0.3.3
Changes since 0.3.2:
- Change
blake3.__module__
from "blake3" to "blake3.blake3". This is
the correct canonical path, related to some Maturin implementation
details. This is intended to help tooling that relies on canonical
paths, but most regular callers don't need to worry about this. See
mkdocstrings/mkdocstrings#451 for an example
of a tool that needs to know this. - Update PyO3 to v0.17.
0.3.2
0.3.1
version 0.3.1
Changes since 0.3.0:
- The experimental C implementation has been bumped to v0.0.1. Testers
and reviewers can install this implementation from TestPyPI with:
pip install -i https://test.pypi.org/simple/ blake3-experimental-c
- We now avoid releasing the GIL for short inputs and release the GIL
for long outputs in addition to long inputs. - The experimental C implementation now has GIL handling matching the
Rust implementation. - Both implementations now contain an internal mutex, to protect the
state object from data races. However, it's still possible for data
races to occur in the input buffer. (This is also the case for
standard hashlib implementations.)