This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
Cython (source)	~=3.0.0 -> ~=3.1.2

---

Release Notes

cython/cython (Cython)

v3.1.2

Compare Source

==================

Bugs fixed

• Attribute lookups failed on the bool builtin type.
  ( issue :issue:6905)

• Type checks on or-ed union types could incorrectly return false.
  ( issue :issue:6420)

• Negative list indexing could accidentally wrap around twice in PyPy and the Limited API.

• Iterating over literal sequences with starred (unpacked) items could infer a wrong
  type for the loop variable and fail to assign the values.
  ( issue :issue:6924)

• Calls to C functions taking exception types failed to check for a None argument.
  ( issue :issue:6420)

• Fused functions had an incorrect __module__ attribute.
  ( issue :issue:6897)

• The type of Cython implemented functions had an incorrect __module__ attribute.
  ( issue :issue:6841)

• Errors while indexing into bytearray or str in nogil sections could crash.
  ( issue :issue:6947)

• bytearray.append() could silently accept some invalid character numbers.

• The C++11 <type_traits> header was included regardless of the C++ version.
  ( issue :issue:6896)

• PyDict_GetItemStringRef() was accidentally used in older Limited API versions.
  ( issue :issue:6914)

• abort() was used but not always available in the Limited API.
  ( issue :issue:6918)

• Some dependencies were missing from the depfile.
  ( issue :issue:6938)

• Embedded function signatures were not always separated from the existing docstring.
  ( issue :issue:6904)

• numpy.math was missing from Cython/Includes/ and could not be cimported.
  ( issue :issue:6859)

• Some tests were adapted for NumPy 2.x.
  ( issue :issue:6898)

• Some C compiler warnings were fixed.
  ( issue :issue:6870)

• Cython.Build was not officially exposing the cythonize function.
  ( issue :issue:6934)

v3.1.1

Compare Source

==================

Bugs fixed

• A reference in the async delegation code was fixed.
  ( issues :issue:6850, :issue:6878)

• Conditional if-else expressions mixing Python and C (numeric) types could end up
  inferring an overly tight result type, thus leading to unexpected type conversions,
  runtime exceptions on assignment, or incorrect "temporary assignment" compile errors.
  ( issue :issue:6854)

• Some Limited API issues were resolved.
  ( issue :issue:6862)

• Large C long long values could be truncated when passed into PyPy.
  ( issue :issue:6890)

• callable() incorrectly reported False in PyPy for classes with metaclasses.
  by Anatolii Aniskovych. ( issue :issue:6892)

• The signature of fused functions was no longer introspectable in Cython 3.1.0.
  ( issue :issue:6855)

• Coroutines could generate invalid C with line tracing enabled.
  ( issue :issue:6865)

• Code using complex() could generate invalid C code missing type declarations.
  ( issue :issue:6860)

• Code using e.g. list[int | None] outside of variable/argument annotations failed to compile.
  ( issue :issue:6856)

• Code using ctuples in a const context could generate invalid C.
  ( issue :issue:6864)

• Accessing special methods on cpdef enums failed to compile.

• Some C compiler warnings were resolved.
  es by Daniel Larraz. ( issues :issue:6876, :issue:3172, :issue:6873, :issue:6877)

• Re-establish support for PyPy 3.8.
  ( issue :issue:6867)

v3.1.0

Compare Source

==================

Other changes

• No functional changes since 3.1.0 rc 2.

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Reviewer's Guide

This pull request updates the Cython dependency from version ~=3.0.0 to ~=3.1.0 in the requirements.txt file.

File-Level Changes

Change	Details	Files
Updated Cython dependency version.	Modified the Cython version from ~=3.0.0 to ~=3.1.0.	requirements.txt

---

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 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!

Customizing Your Experience

Access your dasard 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 .