Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

LGTM considering @zooba's #152433 (comment).

cc @colesbury who tracks mimalloc differences from upstream in #113141.

This change looks fine, if we're maintaining the sources separately. If we're trying to track upstream closely, then we'll need them to make the change first. That's @colesbury's call, it seems.

Our copy of mimalloc is fairly out of date at this point, and does carry several patches against the equivalent upstream version. Regardless, I think we should be sure that this is done upstream before we merge it ourselves, or it's likely to be lost if and when we update our copy -- ideally, when we do such an update we can do it without carrying any patches forward.

Yeah, if it's not CPython specific, please also open a PR in upstream mimalloc.