Skip to content

Add python3.13 supporting - #73

Merged
vadikko2 merged 4 commits into
masterfrom
feature/add-python-313-supporting
Jul 23, 2026
Merged

Add python3.13 supporting#73
vadikko2 merged 4 commits into
masterfrom
feature/add-python-313-supporting

Conversation

@vadikko2

@vadikko2 vadikko2 commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

Python 3.13 Support

This release adds official support for Python 3.13. The minimum required version remains Python 3.10+.

What's Changed

  • Added PyPI classifier Programming Language :: Python :: 3.13
  • Extended CI test matrix to Python 3.13 (lint, type checks, unit & integration tests)
  • Updated release workflow to build on Python 3.10–3.13 and publish to PyPI from Python 3.13
  • Switched CodSpeed benchmarks to Python 3.13
  • Fixed README: minimum version is 3.10+ (was incorrectly listed as 3.9+)

Supported Python Versions

Version Status
3.10 ✅ Supported
3.11 ✅ Supported
3.12 ✅ Supported
3.13 ✅ Supported (new)

Upgrade

No code changes or migration steps are required:

pip install -U python-cqrs

Full Changelog
Add Python 3.13 support
Update CI workflows (tests.yml, python-publish.yml, codspeed.yml)
Fix README minimum Python version

Summary by CodeRabbit

  • New Features
    • Added support for Python 3.13, including package publishing and benchmark compatibility.
  • Tests
    • Expanded automated linting and test coverage to include Python 3.13.
  • Documentation
    • Updated the documented minimum Python version to 3.10.
    • Added Python 3.13 to the supported-version listings.

@vadikko2
vadikko2 requested review from 1owkeyme and lukashuk-da July 23, 2026 10:14
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@vadikko2, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4db1a2cf-1b97-4bcc-9d03-2f84bdf03bbf

📥 Commits

Reviewing files that changed from the base of the PR and between ba0b506 and 610d146.

📒 Files selected for processing (1)
  • pyproject.toml
📝 Walkthrough

Walkthrough

The project now declares Python 3.13 support, documents Python 3.10 as the minimum version, and adds Python 3.13 to testing, benchmarking, and release workflows.

Changes

Python 3.13 support

Layer / File(s) Summary
Support declarations and documentation
pyproject.toml, README.md
Package metadata declares Python 3.13 support, while the README changes the minimum supported version from 3.9 to 3.10.
CI and release matrix
.github/workflows/tests.yml, .github/workflows/codspeed.yml, .github/workflows/python-publish.yml
Linting, tests, and benchmarks run with Python 3.13; package publishing now targets the Python 3.13 release matrix entry.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: adding Python 3.13 support across CI, publishing, benchmarks, and metadata.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/add-python-313-supporting

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codspeed-hq

codspeed-hq Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will improve performance by 31.91%

⚡ 3 improved benchmarks
✅ 67 untouched benchmarks
⏩ 10 skipped benchmarks1

Performance Changes

Benchmark BASE HEAD Efficiency
test_benchmark_complex_nested_structure 218.4 µs 132.5 µs +64.78%
test_benchmark_request_to_dict 68 µs 56.2 µs +20.93%
test_benchmark_response_to_dict 55.3 µs 48 µs +15.19%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.


Comparing feature/add-python-313-supporting (610d146) with master (9a6d6cf)

Open in CodSpeed

Footnotes

  1. 10 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@vadikko2
vadikko2 merged commit 22ec56c into master Jul 23, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant