Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #905 +/- ##
=======================================
Coverage 54.45% 54.45%
=======================================
Files 33 33
Lines 3043 3043
=======================================
Hits 1657 1657
Misses 1386 1386 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ce61415 to
95c2b25
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==0.23.0→==0.25.0Release Notes
indygreg/python-zstandard (zstandard)
v0.25.0Compare Source
Py_REFCNT(obj)instead of accessing(*obj)->ob_refcntdirectly.This fixes a nogil / multi-threaded compile error. (#201, #275)
has been backported. (#272)
PYTHON_ZSTANDARD_IMPORT_POLICYenvironment variable now has leadingand trailing whitespace stripped. Values like
cffiandcffiarenow equivalent to
cffi.cibuildwheelanduv(where possible). This change should be backwardscompatible. But wheel building for this project has historically been
fragile and there may be unwanted changes. We're optimistic that standardizing
on uv (except for musllinux ppc64le and s390x where uv isn't available)
will lead to more stability over time.
tests against a separate build that was theoretically identical. But the
builds may have been subtly different, leading to preventable bugs in our
wheels. (Enabling this test coverage did not uncover any failures.)
pyproject.tomlbuild backend has been switched fromsetuptools.build_meta:__legacy__tosetuptools.build_meta.Modern versions of setuptools broke
--config-settings=--build-option=...as part of implementing PEP 660.A workaround is to use
--config-settings=--global-option=...instead.--global-optionapparently is deprecated and the setuptools folks have yetto figure out how to thread config settings into
setup.pyinvocations.(
--build-optionis sent to thebuild_wheelcommand but not thebuild_editablecommand.)manylinux_2_28(versusmanylinux2014) for older Python versions. This may raise the minimumglibc version, effectively dropping support for Debian 8 and 9, Ubuntu
13.10 through 18.04, Fedora 19 to 28, and RHEL/Centos 7. However, in
practice most platforms don't container newer glibc symbols and are still
ABI compatible with
manylinux2014and glibc 2.17.(#274)
on Python <3.14, as cffi didn't implement free-threaded support until
the 2.0 release. (#274)
formally support free-threaded builds. (#276)
pythoncapi_compat.hfile has been upgraded to the latest version. (#278)setup.pynow depends onpackagingand usespackaging.version.Versionfor version comparisons. This removes some deprecation warnings from usage of
legacy distutils
Versionclasses.to >=1.5.6. (#254, #267)
as
zstandard.backend_c.*versuszstd.*before. The names have beensubtly broken for years. We believe the only practical exposure to this change
is via pickling (possibly encountered when using the
multiprocessingorconcurrent.futurespackages), which would fail to pickle types likeZstdErrorbefore since the fully qualified type name referenced anincorrect and likely missing package (
zstd). (#248)v0.24.0Compare Source
Backwards Compatibility Notes
setup.pywill likely yield a working install. However, this is not officially supported.Changes
pyproject.tomlfile now defines a[project]section.collections.abs.Bufferon Python 3.12+ instead oftyping.ByteString, astyping.ByteStringwas deprecated and later removed. (#238, #262)get_frame_parameters()now accepts an optionalformatargument defining the zstandard frame type. You can pass e.g.zstandard.FORMAT_ZSTD1_MAGICLESSto decode frames without header magic. (#217)Source Archive Publishing Error
During the release process of this version, we uploaded the source archive to PyPI after some wheels. PyPI rejected the source archive because of presence of a
license-fileentry while using metadata version 2.4. We manually generated the source distribution locally. The source distribution on PyPI therefore does not match what GitHub Actions produced.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.