chore(deps): update dependency multidict to v7 #125
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dawid/schulportal-telegram-bot!125
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/multidict-7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==6.9.0→==7.0.0Release Notes
aio-libs/multidict (multidict)
v7.0.0Compare Source
=====
(2026-09-26)
7.0.0 is a major release. It makes :class:
~multidict.istrfinal, adds apublic C API for third-party extensions, and makes the C extension
substantially faster across the board.
Breaking change. :class:
~multidict.istrcan no longer be subclassed,on either backend. Code that subclassed it has to wrap or convert instead.
The C extension also started rejecting an argument passed both
positionally and by name with :exc:
TypeError, where it used to silentlymisbehave.
Public C and Cython API. Other C extensions and Cython modules can now
create, read and mutate multidicts through a capsule, without going through
the Python-level API. The capsule comes with
multidict_capi.h, acimport-ablemultidict/__init__.pxdand:func:
multidict.get_include. The API includesMultiDict_ForEach()anda watchers API modeled on CPython's dict watchers. See the :doc:
C API <capi>and:doc:
Cython API <cyapi>references.Performance. On CodSpeed's GIL-build benchmarks against 6.9.1, 82
C-extension benchmarks got faster and none got slower. Rough figures:
~multidict.CIMultiDictkeyed by plain :class:str: construction,add(),extend(),update()and item assignment got 2 to 3.8times faster, and lookups about 2 times faster.
~multidict.CIMultiDictkeyed by :class:~multidict.istr, andcase-sensitive :class:
~multidict.MultiDict: lookups, insertion anddeletion got 10% to 70% faster.
~multidict.MultiDict.getalland iterating:meth:
~multidict.MultiDict.itemsgot about 35% faster, and the view setoperations 10% to 85% faster.
~multidict.MultiDict.popitemon a whole mapping went fromquadratic to linear time.
lookups got 24% to 33% cheaper on :class:
~multidict.MultiDictand 4 to 5times cheaper on :class:
~multidict.CIMultiDictwith lowercase :class:strkeys, and item assignment 15% to 19% cheaper. Construction and deletion on
:class:
~multidict.MultiDictcost 2% to 7% more. With several threadsmutating at once, a
d[key] = valuegot about four times faster.The pure-Python backend is unchanged in speed.
Robustness. This release fixed several crashes and leaks in the C
extension, including use-after-free bugs when a key's
lower()or avalue's
__eq__mutated a multidict, a crash at interpreter shutdown,and table and reference leaks on the free-threaded build.
Bug fixes
Fixed a segmentation fault in the C extension when a finalizer let the
same multidict be resized while
del md[key]or:meth:
~multidict.MultiDict.popallwas still scanning the table, and aspurious :exc:
RuntimeErrorfrom :meth:~multidict.MultiDict.getallwhen a garbage collection triggered while building its result mutated
the multidict -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1492, :issue:1512.Fixed a reference leak of the key and value in the C extension when
growing the hash table fails with :exc:
MemoryErrorduring:meth:
~multidict.MultiDict.add, :meth:~multidict.MultiDict.update,:meth:
~multidict.MultiDict.merge, :meth:~multidict.MultiDict.setdefaultor item assignment -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1507.Fixed a data race on the free-threaded build of the C extension where a
MultiDict's own version counter was read by:func:
~multidict.getversionand written on every mutation with a plain,non-atomic load and store. Both sides switched to a relaxed atomic
load/store, matching the pattern already used for the object's item
count -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1514.Fixed the C extension discarding a :exc:
MemoryErroror:exc:
KeyboardInterruptraised by a positional argument's__len__while the size of an update was estimated.
extend(),update(),merge()and subclass construction started propagating it, matching thepure-Python backend; only the :exc:
TypeErrorfrom an unusable__length_hint__stayed ignored -- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1517.Ensured that canonical keys in pure-Python :class:
~multidict.MultiDictand:class:
~multidict.CIMultiDictare converted to exact :class:strinstanceswithout invoking :meth:
object.__str__overrides, matching the C extension --by :user:
agustin18.Related issues and pull requests on GitHub:
:issue:
1535.Fixed the argument counts reported by the C extension when a method is
called with too many positional arguments; methods with an optional
second argument claimed to take exactly one, and methods requiring two
claimed to take a range. A method called with none of its two required
arguments now reports both as missing -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1545.Fixed the C extension accepting an argument passed both positionally and
by name instead of raising :exc:
TypeError.md.add("a", key="k", value="v")stored a wrong value, andmd.get("a", "b", key="c")silently ignored the surplus arguments -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1545.Fixed a memory leak in the free-threaded build of the C extension.
:meth:
~multidict.MultiDict.clearhands its hash table to a drain thatfrees it once no lock-free reader is in flight, and a drain that finds
one leaves the table for the next drain to free. Deallocation ran no
drain of its own, so a multidict dropped after such a clear, with no
operation in between, never freed that table nor released the references
its entries still held. Builds with the GIL enabled emit byte-identical
code and are unaffected -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1555, :issue:1562.Fixed a crash during interpreter shutdown in the C extension: a
multidict started keeping a reference to its own module, so the module
state it reads while being torn down could not be freed first
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1563.Fixed retired hash tables lingering in the free-threaded build of the C
extension. A drain that finds a lock-free reader in flight puts the tables
it holds back for the next drain to run, and the reader it saw could
already have looked, so nothing was left to free them: they stayed until
the multidict was next used, and if it was dropped instead, the references
their entries held were never released. Builds with the GIL enabled emit
byte-identical code and are unaffected -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1565.Fixed reference cycles through a multidict going uncollected in the
free-threaded build of the C extension. A hash table waiting to be freed
still owns the references of the entries left in it, and those were not
reported to the garbage collector, which then read the values as reachable
from outside the cycle and kept it alive. Builds with the GIL enabled emit
byte-identical code and are unaffected -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1566.Fixed
extend(),update()andmerge()of the C extensionraising :exc:
SystemErrorwhen given an object whose__length_hint__()reported close to :data:sys.maxsizetogetherwith keyword arguments, and overflowing the table size computation for
such a hint; a hint too large to reserve for is ignored, as
:meth:
list.extenddoes -- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1577.Fixed a use-after-free in the C extension's
MultiDict.__eq__when a value's
__eq__mutated either multidict; comparingexact :class:
strvalues also became faster -- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1579.Fixed a use-after-free in the C extension when a :class:
strsubclasskey's
lower()mutated the source while a:class:
~multidict.CIMultiDictwas built from, extended, updated ormerged with a :class:
dictor a multidict of the other casesensitivity. The extra references this takes are limited to the keys
whose
lower()can run Python code, so other updates do not pay forthem -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1581, :issue:1598.Features
Added a public C and Cython API for third-party extensions. Its
MultiDict_ForEach()family hands a visitor each entry's key, value,identity (the canonical key the mapping looks entries up by, lower-cased
on a :class:
~multidict.CIMultiDict) and the identity's hash-- by :user:
Vizonexand :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1478.Changed the C extension to track the entries that
:meth:
~multidict.MultiDict.getall, item assignment,:meth:
~multidict.MultiDict.update, :meth:~multidict.MultiDict.mergeand :meth:
~multidict.MultiDict.to_dicthave visited in a bitmap privateto the call, instead of temporarily marking entry hashes in the table
itself. Concurrent readers on free-threaded builds no longer have to
tolerate marked entries. Item assignment,
:meth:
~multidict.MultiDict.to_dictand lookups of keys with many valuesgot faster, while :meth:
~multidict.MultiDict.updatewith many repeatedkeys got somewhat slower
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1505.Replaced the C extension's per-key finder object with a single
callback-driven walk in a new
_multilib/walk.hheader. The entries awalk has already reported were tracked by the walk itself rather than
by every caller, and the walk kept its position in registers instead of
reloading it from a struct on each step, so
:meth:
~multidict.MultiDict.getalland the items and keys view setoperations got faster on keys with many values -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1522.Sped up
CIMultiDictoperations keyed by a plainstrin the Cextension. An all-ASCII key was lowered directly instead of through a
str.lower()call, and a key that is already lowercase became its ownidentity, which saved both a copy and a rehash. Looking up a lowercase key
got about three times faster and inserting one about twice as fast, keys
that do carry uppercase gained 20% to 35%, and bulk operations on
already-lowercase keys, such as :meth:
~multidict.MultiDict.extendandconstruction from a :class:
dict, got up to three times faster-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1527.Sped up building an
istrin the C extension. The class gained its ownvectorcall, so the one-argument form stopped packing its argument into a
tuple for :c:func:
!type_callonly to unpack it again with:c:func:
PyArg_ParseTupleAndKeywords. Building anistrfrom a:class:
strgot about 19% faster, and building one from anistr,which hands back the original, about three times faster. In exchange
:meth:
~multidict.MultiDict.getallcosts nine more instructions percall, since the added code moves where the compiler draws its inlining
line -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1537.Sped up building and dropping multidicts in the C extension by reusing
freed hash tables instead of returning them to the allocator. Small
tables are kept in a bounded per-size-class pool held in the module
state, the way CPython reuses key objects for :class:
dict. Only onbuilds with the GIL: a shared pool needs an atomic exchange to take a
table and another to put one back, which measured slower than the
per-thread allocator a free-threaded build already has
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1539.Sped up :meth:
~multidict.MultiDict.copy, constructing a multidict fromanother one, and growing one past its current size in the C extension, by
not zeroing the parts of a hash table that are about to be overwritten. A
copied table is overwritten in full, and a resized one has the entries it
carries over written straight onto it -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1540.Sped up :meth:
~multidict.MultiDict.items,:meth:
~multidict.MultiDict.keys, :meth:~multidict.MultiDict.valuesand iterating a multidict in the C extension, by reusing the view and
iterator objects they allocate instead of returning them to the
allocator -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1541.Sped up constructing a :class:
~multidict.MultiDict,:class:
~multidict.CIMultiDict, :class:~multidict.MultiDictProxyor:class:
~multidict.CIMultiDictProxyin the C extension, by reusing theobject itself as well as its hash table. Subclasses are unaffected and
keep allocating as before -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1542.Sped up :meth:
~multidict.MultiDict.getallin the C extension, byshrinking the scratch buffer the walk carries on the stack from 4 KB to
1 KB. The buffer was large enough to stop the compiler inlining the walk
into its callers, which cost more than it saved -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1543.Sped up lock-free reads on the free-threaded build of the C extension.
Every reader that leaves a :class:
~multidict.MultiDictlast used tocall into the retired-table drain, whose first act is a sequentially
consistent read-modify-write, even though the retired list is empty
almost every time; a plain load took over that case and the drain
itself moved out of line.
key in mdgot about 10% cheaper,md[key]about 8% and a missingmd.get(key)about 5%, measured asinstruction counts on CPython 3.14. Builds with the GIL enabled emit
byte-identical code and are unaffected -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1546.Added a watchers C API, so another C extension can be notified when a
:class:
~multidict.MultiDictor :class:~multidict.CIMultiDictchanges.It follows CPython's :c:func:
!PyDict_AddWatcherfamily, with twodifferences: the callback is passed two context pointers, one fixed per
registered callback and one per watched multidict, and events are
delivered once the operation that produced them has finished rather than
mid-mutation. The events are multi-value aware, and each one that concerns
a key carries the identity and its hash alongside it. Up to
:c:macro:
MULTIDICT_MAX_WATCHERS(32) watchers can be registered, and afailing callback is reported through :func:
sys.unraisablehookwith theevent and the multidict's type and address, as CPython does for dict
watchers -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1551.Sped up lookups, insertions and deletions in the C extension by always
inlining the hash-table probe's initializer. Left to itself the compiler
emitted it out of line, so every probe opened with a call for five
stores. Free-threaded builds already inlined it and are unchanged
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1554.Sped up every method call on :class:
~multidict.CIMultiDictand:class:
~multidict.CIMultiDictProxyin the C extension by bindingtheir method descriptors to the class itself instead of inheriting
them from :class:
~multidict.MultiDictand:class:
~multidict.MultiDictProxy; CPython only specializes amethod call when the descriptor belongs to the exact type of the
receiver, so every such call was taking the generic path
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1567.Made :meth:
~multidict.MultiDict.popitemin the C extension drop thetrailing deleted entries it walked over, so that popping every item
out of a mapping costs linear time rather than quadratic; the
pure-Python implementation already did this -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1568.Sped up iterating over :meth:
~multidict.MultiDict.itemsin the Cextension by handing out the same
(key, value)tuple again whenthe caller has already let go of it, as
for key, value in d.items()does on every step; a tuple the caller keeps is leftalone and a new one is used from then on -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1569.Sped up lookups on the free-threaded build by comparing the hash before
touching an entry's key and by matching a key that is the very same
object as the one looked up without taking a reference to it, so the
common hit costs two fewer atomic operations -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1570.Sped up mutations on the free-threaded build when several threads
mutated multidicts at the same time: each thread reserved version
numbers in batches instead of bumping one counter shared by every
thread on each mutation, so with six threads a
d[key] = valuewasabout four times faster -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1587, :issue:1599.Sped up the C extension by keeping the table resize on the insert path and
the operations behind Python slots out of line, so they stopped crowding the
hot paths out of the compiler's inlining budget. On GIL builds, building a
multidict from 200 pairs got about 4% faster in instruction count and
inserting a new key about 2%; on free-threaded builds, key lookups got up to
5% faster -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1600, :issue:1601.Removals and backward incompatible breaking changes
Made :class:
~multidict.istra final class to disallow subclassing in boththe C extension and pure-Python implementations -- by :user:
agustin18.Related issues and pull requests on GitHub:
:issue:
1535.Improved documentation
Documented how :class:
~multidict.MultiDictand:class:
~multidict.CIMultiDictcompare with :class:dicton both thedefault and the free-threaded builds, with per-operation measurements,
and how to run the benchmarks in a stable environment
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1532.Documented what :class:
~multidict.istrkeys are worth on a:class:
~multidict.CIMultiDict, as instruction counts next to theequivalent plain :class:
strkeys. The advice to create them once andreuse them was already there; the numbers behind it were not
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1547.Documented that a few rows of the benchmarking reference are measured on
an empty or 20-item mapping rather than the 200-item one the section
describes -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1558.Mentioned in the README and docs index that
multidictis optimized forboth the GIL and free-threaded builds, and that its performance is typically
within 20-30% of :class:
dictfor common operations, with a link to thebenchmarks page for the full breakdown -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1559.Fixed the C extension's
popone()andpop()docstrings, whichclaimed the last occurrence of the key was removed; the first one is,
as on the pure-Python backend. Added a note on rejecting duplicate
values for keys that must carry exactly one, such as security-sensitive
HTTP headers -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1578.Added a C API example of a watcher that invalidates a cache: it unwatches
from its own callback, watches again on the next rebuild, and gives up
on a multidict that keeps changing -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1586.Refreshed the tables in the benchmarking reference for the 7.0.0 release,
and replaced the range quoted for the pure-Python backend with its average
slowdown -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1602.Packaging updates and notes for downstreams
Removed the C extension code path that existed only for free-threaded
Python 3.13, whose support was dropped in v6.8.0. The free-threaded
build started requiring CPython 3.14 or newer and failing with a clear
compiler error on older free-threaded interpreters; builds with the GIL
enabled were unaffected and still go down to Python 3.10
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1524.Contributor-facing changes
Added CodSpeed benchmarks for
getall()on a large table,update()with duplicate keys,
merge(),to_dict()and items view containmentwith duplicate keys -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1506.Added CodSpeed benchmarks for
getall()on keys with many values, bothin a small table and in a table large enough to need a heap allocated
bitmap -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1509.Moved the compiler hint macros used by the C extension out of
htkeys.hintocompiler.hand dropped theHT_prefix fromtheir names -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1510.Moved the debug-only
ASSERT_CONSISTENTmacro and the_md_check_consistency()and_md_dump()helpers used by the Cextension out of
hashtable.hinto their owndebug.hheader-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1513.Added CodSpeed benchmarks for
CIMultiDictkeyed by plainstrinsteadof
istr, covering already-lowercase, mixed-case and non-ASCII keys-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1521.Documented that the pure-Python test leg needs
--no-c-extensionsalongside
MULTIDICT_NO_EXTENSIONS=1; the environment variable picksthe backend that gets imported, but only the flag deselects the
C-extension half of the test matrix -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1523.Documented how to run the Hypothesis property tests, which a default
pytestrun excludes via the-m "not hypothesis"markerexpression in
pytest.iniand whose pinmake install-devdoesnot install -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1525.Added
tools/codegen_diff.py, which reports the functions GCC emitsdifferently before and after a change to the C extension. Addresses,
RIP-relative displacements and branch offsets inside a symbol are
normalized away first, so a single instruction-length change no longer
makes every later function look modified, while constants and structure
offsets are left alone so that a real change is not folded away. A tree
that fails to build is reported by name rather than compared
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1529.Fixed
benchmarks/istr.pyto importpyperfunder its currentname; it had been failing to start since the package was renamed from
perf-- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1531.Rewrote the benchmark scripts around a single registry of benchmarked
operations, and added a Callgrind driver that records deterministic
instruction counts per operation. The measurements of destructive
operations such as
pop()andclear()stopped counting the costof rebuilding the mapping -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1532.Moved the bulk
extend(),update()andmerge()paths of the Cextension out of
hashtable.hinto their ownbulk_update.hheader, leaving
hashtable.hto the table itself and the single-keyoperations -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1533.Moved the two list-reading helpers behind
itemsview.__contains__()andthe
extend()/update()/merge()sequence parser out ofhashtable.hand into a newmultidict/_multilib/unpack.h, together witha shared
unpack_pair()that both call to read a(key, value)pair out of an exact two-element tuple or list. C extension only; the pure
Python implementation has no header layout to mirror
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1534.Added a
MULTIDICT_NO_FREELIST=1build option that stops the Cextension reusing freed blocks. A reused block never reaches
free(),so AddressSanitizer can neither poison it nor report a use-after-free on
it; an instrumented run wants a second pass with this set, as
AGENTS.mddescribes.Also added a private
_freelist_clear()to the C extension, for teststhat inject an allocation failure: a reused block lets an operation run
without calling the allocator at all, which would put the recovery path
out of reach -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1539.Added a visitor to the public C API test harnesses that mutates the multidict
it is walking, covering the reentrancy guard in
MultiDict_ForEach()fromboth
multidict._testcapiandmultidict._testcyapi-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1544.Added benchmarks for the shapes where an allocation is most of the work:
an empty mapping, a 20-item one built or copied, a view or an iterator
taken on its own, and a proxy. The allocation an operation makes is a
fixed cost, so at the existing 200-item size it was divided across 200
entries and all but vanished;
d.items()measured 1.7% faster whereit is 46% faster -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1556.Sorted
docs/spelling_wordlist.txtcase-insensitively, and documentedin
AGENTS.mdthat it is to be re-sorted rather than appended to. Thelist had grown in append order, which made a word hard to find and put
every PR adding one on the same last line -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1557.Stopped asking every performance pull request to regenerate the tables in
the benchmarking reference, since each run shifts every row slightly and the
churn hides the rows that moved, and moved the refresh to once per release.
Added :file:
RELEASE.md, which documents the release procedure, includingthat refresh -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1564.Renamed the C extension's internal helpers in the
_multilibheadersso that a leading underscore marks exactly the functions used only
within their own header; type slots and method callbacks keep their
names -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1571.Spelled out in
AGENTS.mdthat every verb in a news fragment ispast tense, and added a bad and good example pair plus a matching
"Things not to do" entry -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1588.Changed the release workflow to rewrite the Sphinx roles of the changelog
section as Markdown before publishing it as the GitHub Release body, so
that class, method and exception references, contributor handles and
documentation links render there instead of showing as raw markup
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1596.Miscellaneous internal changes
Changed the internal
htkeys_build_indices()helper in the Cextension to return
void; it cannot fail, so both callers werechecking for an error that never occurred -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1516.Routed every field of the C extension's hash table that more than one
thread can reach through a named accessor in the new
_multilib/freethreading.hheader, instead of each call site choosingbetween an atomic and a plain access behind
#ifdef Py_GIL_DISABLED.Each accessor kept the operation and memory ordering its call sites
already used, so neither build changed behavior -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1518.Removed
get_mod_state_by_cls(), an unused helper in the C extension-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1520.Documented why
md_clear()keeps clearing entry fields withPy_CLEAR()on the GIL build rather than routing them through_multilib/freethreading.h:Py_CLEAR()skips the store when afield is already
NULL, so no accessor there is a substitute for it-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1526.Collapsed the two
#ifdef Py_GIL_DISABLEDarms that fill in a freshlyinserted hash table entry in the C extension into one. Both builds started
writing the entry's fields in the order the free-threaded build needs, and
publishing the value without first loading and releasing the one already
there, since a fresh entry holds none -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1528.Merged the C extension's deferred-decref accumulator into
reflist_t,so one collector of strong references, in the
_multilib/reflist.hheader, came to serve both the callers that build a result list and the
ones that postpone a decref until a mutation finishes. Its storage became an
inline array that spills into a chain of heap blocks, which also made
:meth:
~multidict.MultiDict.getalla little faster on keys with manyvalues, since the collected values stopped being copied to a bigger
buffer as they accumulate -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1530.Dropped two module state lookups in the C extension that had already been
answered elsewhere.
MultiDict.__init__()andCIMultiDict.__init__()switched to reading the state pointer that
tp_new()stored on the object insteadof resolving it from the type a second time, and an
istrstoppedcarrying a state pointer of its own, which was written on every creation
and never read. Constructing a subclass of either container got about 1%
cheaper, and every
istris eight bytes smaller-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1536.Narrowed the critical section of the single-key methods (
add(),__setitem__(),__delitem__(),setdefault(),pop(),popone(),popall()andgetall()): a key is converted to itsidentity and hashed before the lock is taken, rather than while a
free-threaded build holds the multidict locked -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1538.Changed
MultiDict_ForEach()to walk every entry with a linear scaninstead of the resumable iterator cursor, which its caller does not need while
it holds the critical section for the whole walk -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1544.Sped up the argument parsing of the C extension. The all-positional form
of every method taking
keystarted binding its arguments inline instead ofcalling into the keyword machinery, and keyword names were matched against
interned parameter names by identity before falling back to a string
comparison -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1549.Stopped building the implicit :data:
Nonedefault ofMultiDict.get()on every call in the C extension, and produced it only when the key is
actually missing -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1549.Laid out the common branch in line in the single-key lookup probe loop and in
the key to identity conversion: the deleted-slot check and the
strsubclass check were marked as the rare cases, so the compiler stopped putting
the frequent path behind a taken branch -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1550.Stopped building the implicit :data:
Nonedefault ofMultiDict.setdefault()on every call in the C extension -- by:user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1553.Reordered the fields of the C extension's multidict object so the ones a
lookup reads share a cache line, and dropped its separate module
reference in favor of the one the module state already holds, which
made every multidict 16 bytes smaller -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1584.Dropped the C extension's
multidict_tp_traverse()andmultidict_tp_clear()wrappers;md_traverse()andmd_clear()now serve as the type's GC slots directly -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1589.Removed a redundant
NULLcheck and a strayPyErr_Format()argument from the C constructors, and an always true condition from the
pure Python
getall()-- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1590.Merged the duplicated
__init__()bodies of the CMultiDictandCIMultiDictinto one helper -- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1591.Replaced the allocate, set state and take the module reference sequence
repeated across the C constructors with one helper -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1592.Renamed internal helpers whose names no longer matched what they did,
and fixed misspelled docstring identifiers in the C extension
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1593.Renamed the C extension's functions that are used only as type slots
after the slot they fill, as
<type>_tp_<slot>,<type>_nb_<slot>,<type>_sq_<slot>or<type>_mp_<slot>-- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1594.Replaced the custom
tp_newslots that blocked direct instantiation ofthe C view and iterator types with
Py_TPFLAGS_DISALLOW_INSTANTIATION-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1595.v6.9.1Compare Source
=====
(2026-09-21)
Bug fixes
Fixed the C extension reading freed memory on free-threaded builds when a
list handed to :py:meth:
~multidict.MultiDict.update,:py:meth:
~multidict.MultiDict.extend, :py:meth:~multidict.MultiDict.mergeor the :py:class:
~multidict.MultiDictand :py:class:~multidict.CIMultiDictconstructors, a
[key, value]item inside any iterable handed to them, or alist tested with
inagainst :py:meth:~multidict.MultiDict.items, ischanged by another thread; a call that catches the list shrinking under it
now raises :py:exc:
RuntimeError-- by :user:rodrigobnogueira.Related issues and pull requests on GitHub:
:issue:
1437.Fixed a data race on the free-threaded build where a retired hash table's
reader count used relaxed atomics, letting a lock-free
get()/getone()/__getitem__()read race a concurrent free of that table. The reader-exitdecrement and the drain's free check now use release/acquire ordering
instead -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1481.Fixed a free-threaded build bug where two threads calling
update(),merge(), or__setitem__()on the same key at the same time could losethe key entirely instead of just racing on which value wins. A decref of the
replaced value could transiently suspend the writer's critical section,
letting a second writer for the same key observe the first writer's
in-progress entry as absent and, once both settled, mistake it for a stale
duplicate and delete it. Every such decref is now deferred until the writer
has released its critical section, so the window can no longer open.
setdefault()had an unrelated instance of the same blind spot (it couldinsert a duplicate rather than recognizing an in-flight key), fixed alongside
it -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1483.Fixed a free-threaded build bug where
getall()and theitems()/keys()/values()equality path could raiseKeyErroror report apresent, never-deleted key as missing. A concurrent
update()/extend()/__setitem__()call can have its critical section transiently suspended(a decref triggering a blocking allocator call) while an entry is marked as
part of its own bookkeeping; a reader landing in that window used to treat
the mark as "not found" instead of "still there, in flight" -- by
:user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1484.Fixed a reference leak in the C extension where
operand | md.items()and
md.items() - operandleaked one key and one value reference perelement of
operand, letting a large operand grow memory without bound(:gh:
GHSA-54p9-h82j-f925 <aio-libs/multidict/security/advisories/GHSA-54p9-h82j-f925>)-- by :user:
asvetlov.The issue was reported by :user:
waydeshi.Related commits on GitHub:
:commit:
350b4a0.Fixed a segmentation fault on the standard (non-free-threaded) C extension
build when a value type's
__del__released the GIL (for example bycalling
time.sleep()) whileupdate(),merge(),__setitem__(),__delitem__(),pop(),popone(), orpopall()was dropping areplaced or removed value.
Py_BEGIN_CRITICAL_SECTIONcompiles to a no-opon this build, so nothing else was stopping a second thread from mutating the
very same
MultiDictconcurrently once the GIL was released mid-mutation.Every such decref is now deferred until the mutation has fully finished, the
same technique already used to close the analogous free-threaded-build race
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1489.Fixed the C extension reading freed memory while iterating a
:py:class:
~multidict.CIMultiDictwhose keys are plain :py:class:str.Converting such a key to :py:class:
~multidict.istrcould run Python code(a :py:class:
strsubclass's__str__or__del__) or, on free-threadedbuilds, suspend the iterator's critical section, after which the iterator read
the entry again even though a concurrent mutation could already have freed it.
As part of the fix, :py:meth:
~multidict.MultiDict.copyand re-initializingfrom another multidict now assign a new version in the C extension instead of
reusing the source's, matching the pure Python implementation
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1496.Fixed a use-after-free on the free-threaded build where a lock-free
get(),[]orincould read a hash table that a concurrentresize had just retired and another reader was freeing
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1497.Contributor-facing changes
Removed a redundant
includeand a duplicatedexcludeline fromMANIFEST.in; sdist contents are unchanged -- by :user:asvetlov.Related issues and pull requests on GitHub:
:issue:
1478.Added
.claudeignorefile -- by :user:asvetlovRelated issues and pull requests on GitHub:
:issue:
1479.Scaled up the pure-Python
pop(),popitem(),__delitem__(),add()and item-insertion benchmarks to do more work per measurement.Repeated CodSpeed runs on the same commit showed these particular
benchmarks flagged as dominated by syscalls, understating their real
cost and adding noise to the reported values; a larger working set
amortizes that overhead -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1485.Replaced deprecated instrumentation codspeed mode with simulation -- by :user:
asvetlovRelated issues and pull requests on GitHub:
:issue:
1493.Reorganized the mutating benchmarks (item insertion,
update(),add()of the same key,pop(),popitem(),clear(),__delitem__()and__setitem__()) to copy a fresh multidict andapply the operation in a loop, like the
add()andextend()benchmarks already do. The insertion,
update()andclear()benchmarks previously mutated a single multidict shared across
rounds, so only the first round measured the intended operation; the
rest did a single copy per round, letting per-round overhead dominate
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1494.The
repr()and view inequality benchmarks were updated to repeat theiroperation in a loop, like the other benchmarks, and the CodSpeed benchmark
job was moved to Python 3.14 -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1498.Dropped
-Ifrom the AddressSanitizer test command inAGENTS.mdand in the CI job. It implies
-E, which made Python ignorePYTHONMALLOC=malloc, so small hash tables were still served frompymallocarenas where use-after-free went undetected-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1499.The CI/CD workflow was updated to stop superseded runs of the same pull request
when a new commit is pushed; runs on
master, release branches, tags,the merge queue, and the daily schedule are never interrupted
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1500.The release job was changed to upload distributions and their signatures
to the GitHub Release one file at a time, skipping assets that were
already attached and retrying after a pause, so that a parallel upload
burst no longer tripped the GitHub secondary rate limit
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1503.Miscellaneous internal changes
Corrected several comments in the free-threaded C extension that
attributed critical-section suspension to a blocking
PyMem_Malloc()call; allocation alone never suspends an acquired critical section, and
the real risk at those sites is a decref running
a finalizer or weakref callback. Also dropped a retry loop in
md_clone_from_ht()that guarded against the same, non-existentallocation-triggered suspension -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1486.Changed the free-threaded build's deferred decref buffer, used by
update()and__setitem__(), to a chain of fixed-size blockswith a large inline first block instead of a small inline array that
was reallocated on growth -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
1501.Configuration
📅 Schedule: (UTC)
🚦 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 was generated by Mend Renovate. View the repository job log.
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.