Bump pyo3 from 0.18.3 to 0.24.1

[dependabot]

Bumps pyo3 from 0.18.3 to 0.24.1.

Release notes

Sourced from pyo3's releases.

v0.24.1

This release is a security fix for the PyString::from_object method, which passed &str data to the Python C API without checking for a terminating nul byte. All historical PyO3 versions are affected, and we recommend you upgrade if you are using PyString::from_object. Thank you to @​vthib for the report and @​Dr-Emann for the fix. A RUSTSEC advisory will be published shortly.

Aside from the security fix, this release contains a number of other non-breaking additions:

• An abi3-py313 feature to support compiling with the Python 3.13 stable ABI.
• PyAnyMethods::getattr_opt to get optional attributes without paying the cost of a Python exception when the attribute in question does not exist.
• Constructor for PyInt::new.
• with_critical_section2 for locking two objects at the same time on the free-threaded build.
• Fix for a PyO3 0.24.0 regression with Option<&str> and Option<&T> (where T: PyClass) function arguments no longer being permitted

There are also a few other small bug fixes for edge cases, mostly related to compile errors from PyO3's macro code.

Thank you to the following contributors for the improvements:

@​bschoenmaeckers @​davidhewitt @​Dr-Emann @​emmagordon @​epontan @​Icxolu @​IvanIsCoding @​jelmer @​jonaspleyer @​ngoldbaum @​Owen-CH-Leung @​Tpt @​Trolldemorted @​XuehaiPan

PyO3 0.24.0

This release is an incremental improvement of refinements and optimizations following the new APIs established in PyO3's last few releases.

Support for jiff datetime conversions have been added, and also UUID conversions.

The FromPyObject derive macro has gained new #[pyo3(default = ...)] and #[pyo3(rename_all = ...)] options, and the IntoPyObject derive macro has gained a new #[pyo3(into_py_with = ...)] option.

PyO3 will now pass positional arguments to Python functions using the "vectorcall" protocol in many cases, which should be an optimization over the previous behaviour (of creating a Python tuple of positional arguments).

Many methods on iterators of Python collections have been optimized.

There are also many other incremental improvements, bug fixes and smaller features.

Thank you to everyone who contributed code, documentation, design ideas, bug reports, and feedback. The following contributors' commits are included in this release:

@​0x676e67 @​alex @​arielb1 @​bschoenmaeckers @​davidhewitt

... (truncated)

Changelog

Sourced from pyo3's changelog.

[0.24.1] - 2025-03-31

Added

• Add abi3-py313 feature. #4969
• Add PyAnyMethods::getattr_opt. #4978
• Add PyInt::new constructor for all supported number types (i32, u32, i64, u64, isize, usize). #4984
• Add pyo3::sync::with_critical_section2. #4992
• Implement PyCallArgs for Borrowed<'_, 'py, PyTuple>, &Bound<'py, PyTuple>, and &Py<PyTuple>. #5013

Fixed

• Fix is_type_of for native types not using same specialized check as is_type_of_bound. #4981
• Fix Probe class naming issue with #[pymethods]. #4988
• Fix compile failure with required #[pyfunction] arguments taking Option<&str> and Option<&T> (for #[pyclass] types). #5002
• Fix PyString::from_object causing of bounds reads whith encoding and errors parameters which are not nul-terminated. #5008
• Fix compile error when additional options follow after crate for #[pyfunction]. #5015

[0.24.0] - 2025-03-09

Packaging

• Add supported CPython/PyPy versions to cargo package metadata. #4756
• Bump target-lexicon dependency to 0.13. #4822
• Add optional jiff dependency to add conversions for jiff datetime types. #4823
• Add optional uuid dependency to add conversions for uuid::Uuid. #4864
• Bump minimum supported inventory version to 0.3.5. #4954

Added

• Add PyIterator::send method to allow sending values into a python generator. #4746
• Add PyCallArgs trait for passing arguments into the Python calling protocol. This enabled using a faster calling convention for certain types, improving performance. #4768
• Add #[pyo3(default = ...'] option for #[derive(FromPyObject)] to set a default value for extracted fields of named structs. #4829
• Add #[pyo3(into_py_with = ...)] option for #[derive(IntoPyObject, IntoPyObjectRef)]. #4850
• Add FFI definitions PyThreadState_GetFrame and PyFrame_GetBack. #4866
• Optimize last for BoundListIterator, BoundTupleIterator and BorrowedTupleIterator. #4878
• Optimize Iterator::count() for PyDict, PyList, PyTuple & PySet. #4878
• Optimize nth, nth_back, advance_by and advance_back_by for BoundTupleIterator #4897
• Add support for types.GenericAlias as pyo3::types::PyGenericAlias. #4917
• Add MutextExt trait to help avoid deadlocks with the GIL while locking a std::sync::Mutex. #4934
• Add #[pyo3(rename_all = "...")] option for #[derive(FromPyObject)]. #4941

Changed

• Optimize nth, nth_back, advance_by and advance_back_by for BoundListIterator. #4810
• Use DerefToPyAny in blanket implementations of From<Py<T>> and From<Bound<'py, T>> for PyObject. #4593
• Map io::ErrorKind::IsADirectory/NotADirectory to the corresponding Python exception on Rust 1.83+. #4747
• PyAnyMethods::call and friends now require PyCallArgs for their positional arguments. #4768
• Expose FFI definitions for PyObject_Vectorcall(Method) on the stable abi on 3.12+. #4853
• #[pyo3(from_py_with = ...)] now take a path rather than a string literal #4860

... (truncated)

Commits

• a213b36 release: 0.24.1 (#5021)
• d85a02d split PyFunctionArgument to specialize Option (#5002)
• c37a50a Add example of more complex exceptions (#5014)
• dcacb9b Simplify PyFunctionArgument impl on &Bound<T> (#5018)
• 03c31c5 fix #[pyfunction] option parsing (#5015)
• 0f49eb1 docs: Remove examples with outdated PyO3 and unmaintained projects (#4952)
• 1b00b0d implement PyCallArgs for borrowed types (#5013)
• 5caaa37 fix: convert to cstrings in PyString::from_object (#5008)
• 4aca459 docs: guide - add link to tables and traits (#5001)
• 0452c0e replace quansight-labs/setup-python with actions/setup-python (#5007)
• 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.

Summary by Sourcery

Upgrade pyo3 dependency from version 0.18.3 to 0.24.1, incorporating security fixes and new features

Bug Fixes:

• Fixes a security vulnerability in PyString::from_object method that could cause out-of-bounds reads

Enhancements:

• Adds support for Python 3.13 stable ABI
• Introduces new methods like PyAnyMethods::getattr_opt and PyInt::new
• Improves iterator performance and optimization

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the pyo3 dependency from version 0.18.3 to 0.24.1. This involves updating the Cargo.toml and Cargo.lock files to reflect the new version.

Updated class diagram for PyAnyMethods

classDiagram
    class PyAnyMethods {
        +getattr_opt(name: &str) : PyResult<Option<PyObject>>
    }
    note for PyAnyMethods "Added getattr_opt to get optional attributes without exceptions."

Loading

Updated class diagram for PyInt

classDiagram
    class PyInt {
        +new(value: i32) : Self
        +new(value: u32) : Self
        +new(value: i64) : Self
        +new(value: u64) : Self
        +new(value: isize) : Self
        +new(value: usize) : Self
    }
    note for PyInt "Added constructor for PyInt::new with various number types."

Loading

File-Level Changes

Change	Details	Files
The pyo3 dependency was bumped from version 0.18.3 to 0.24.1.	Updated the pyo3 version in Cargo.toml. Updated the pyo3 version in Cargo.lock.	Cargo.toml Cargo.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!