Bump pyo3 from 0.22.0 to 0.22.4 in /test-crates/lib_with_disallowed_lib

[dependabot]

Bumps pyo3 from 0.22.0 to 0.22.4.

Release notes

Sourced from pyo3's releases.

PyO3 0.22.4

This release is a security fix for PyO3 0.22.0 through 0.22.3.

The PyWeakrefMethods trait functions for reading borrowed values from Python weak references have been identified as unsound, because they did not account for the possibility the last strong reference could be cleared at any time, leading the borrowed value to be dangling and risk of use-after-free.

PyO3 0.22.4 protects against this issue by making these methods permanently leak strong references. The methods are also marked deprecated and will be removed in PyO3 0.23. Users should switch to use the use PyWeakrefMethods functions which return owned references (the deprecation messages indicate the appropriate upgrade paths).

These functions were added in PyO3 0.22.0; all versions from 0.22.0 through 0.22.3 have been yanked.

Aside from the security fix, PyO3 0.22.4 contains a number of other bugfixes, including:

• A fix for cases where __traverse__ functions of base types were not called when using #[pyclass(extends = ...)]
• A fix for a regression in 0.22.3 where PyO3 generated code would trigger compile failures with crates using #![forbid(unsafe_code)]

Thank you to the following contributors for the improvements:

@​davidhewitt @​ngoldbaum @​exg @​Icxolu

PyO3 0.22.3

This release contains a number of quality improvements building upon PyO3 0.22.2.

Python function calls (using .call0(), .call1(args) and .call(args, kwargs)) will now make use of the "vectorcall" calling conventions where possible, which can reduce overheads in many cases.

There have been several fix-ups to PyO3's FFI definitions. A new pyo3::ffi::compat namespace has been added which offers some backwards-compatible implementations of Python APIs otherwise normally only available on recent Pythons.

There have been numerous other bug-fixes and minor tweaks to improve user experience.

Thank you to the following contributors for the improvements:

@​birkenfeld @​ChayimFriedman2 @​csernazs @​davidhewitt @​Icxolu @​jakelishman @​LilyFoote @​ngoldbaum @​Zyell

PyO3 0.22.2

This release contains some minor reliability fixes building upon PyO3 0.22.1.

As PyO3 is still working on supporting freethreaded Python (upcoming in 3.13), support has been gated behind an UNSAFE_PYO3_BUILD_FREE_THREADED=1 environment variable to avoid unsuspecting users running into broken builds.

Packages built for the abi3 stable ABI will now use FFI functions for refcounting instead of inline reference count modifications on all versions of the stable ABI (previously only abi3 builds for 3.12 and up would use FFI functions). This helps mitigate interactions of old versions of the stable ABI with future CPython releases which do more complex reference counting (e.g. immortal objects, freethreaded reference counting).

The #[pymodule] declarative module now supports directly receiving options. (E.g. #[pymodule(name = "foo")], which would previously have been written as two attributes #[pymodule] #[pyo3(name = "foo")].)

... (truncated)

Changelog

Sourced from pyo3's changelog.

[0.22.4] - 2024-10-12

Added

• Add FFI definition PyWeakref_GetRef and compat::PyWeakref_GetRef. #4528

Changed

• Deprecate _borrowed methods on PyWeakRef and PyWeakrefProxy (just use the owning forms). #4590

Fixed

• Revert removal of private FFI function _PyLong_NumBits on Python 3.13 and later. #4450
• Fix __traverse__ functions for base classes not being called by subclasses created with #[pyclass(extends = ...)]. #4563
• Fix regression in 0.22.3 failing compiles under #![forbid(unsafe_code)]. #4574
• Workaround possible use-after-free in _borrowed methods on PyWeakRef and PyWeakrefProxy by leaking their contents. #4590
• Fix crash calling PyType_GetSlot on static types before Python 3.10. #4599

[0.22.3] - 2024-09-15

Added

• Add pyo3::ffi::compat namespace with compatibility shims for C API functions added in recent versions of Python.
• Add FFI definition PyDict_GetItemRef on Python 3.13 and newer, and compat::PyDict_GetItemRef for all versions. #4355
• Add FFI definition PyList_GetItemRef on Python 3.13 and newer, and pyo3_ffi::compat::PyList_GetItemRef for all versions. #4410
• Add FFI definitions compat::Py_NewRef and compat::Py_XNewRef. #4445
• Add FFI definitions compat::PyObject_CallNoArgs and compat::PyObject_CallMethodNoArgs. #4461
• Add GilOnceCell<Py<T>>::clone_ref. #4511

Changed

• Improve error messages for #[pyfunction] defined inside #[pymethods]. #4349
• Improve performance of calls to Python by using the vectorcall calling convention where possible. #4456
• Mention the type name in the exception message when trying to instantiate a class with no constructor defined. #4481

Removed

• Remove private FFI definition _Py_PackageContext. #4420

Fixed

• Fix compile failure in declarative #[pymodule] under presence of #![no_implicit_prelude]. #4328
• Fix use of borrowed reference in PyDict::get_item (unsafe in free-threaded Python). #4355
• Fix #[pyclass(eq)] macro hygiene issues for structs and enums. #4359
• Fix hygiene/span issues of '#[pyfunction] and #[pymethods] generated code which affected expansion in macro_rules context. #4382
• Fix unsafe_code lint error in #[pyclass] generated code. #4396
• Fix async functions returning a tuple only returning the first element to Python. #4407
• Fix use of borrowed reference in PyList::get_item (unsafe in free-threaded Python). #4410
• Correct FFI definition PyArg_ParseTupleAndKeywords to take *const *const c_char instead of *mut *mut c_char on Python 3.13 and up. #4420

... (truncated)

Commits

• dff9723 release: 0.22.4
• 3330bf2 fix garbage collection in inheritance cases (#4563)
• 8b23397 ci: pypy 3.7 macos on x64 still
• ce63713 ci: run benchmarks on ubuntu 22.04 (#4609)
• b1173f5 ci: fix more ubuntu-24.04 failures (#4610)
• 7371028 ci: move more jobs to macOS arm (#4600)
• 8e3dc45 avoid calling PyType_GetSlot on static types before Python 3.10 (#4599)
• 969300d leak references for safety in PyWeakRefMethods::upgrade_borrowed (#4590)
• d01fbab fix case of gil-refs feature breaking create_exception! macro (#4589)
• 9a641f7 fix unintentional unsafe_code trigger (#4574)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.