Skip to content

⬆️ update Python version support to include 3.13 and drop 3.8 support #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 13, 2025

Conversation

techouse
Copy link
Owner

This pull request includes changes to update the supported Python versions and corresponding configurations in various files. The primary change is the removal of support for Python 3.8 and the addition of support for Python 3.13.

Updates to supported Python versions:

Documentation and configuration updates:

  • CONTRIBUTING.md: Updated the list of supported Python versions to include Python 3.13 and remove Python 3.8.
  • pyproject.toml: Updated the requires-python field, classifiers, target versions for the Black tool, and the python_version for MyPy to reflect the removal of Python 3.8 and the addition of Python 3.13. [1] [2] [3] [4]
  • tox.ini: Removed Python 3.8 from the envlist and gh-actions sections, and added Python 3.13.

@techouse techouse added the dependencies Pull requests that update a dependency file label Mar 12, 2025
@techouse techouse self-assigned this Mar 12, 2025
Copy link

coderabbitai bot commented Mar 12, 2025

Walkthrough

The changes update the project’s Python version support by replacing configurations based on Python 3.8 with those for Python 3.13. The CI workflow file and tox settings have been modified to remove Python 3.8 references and integrate Python 3.13, including updated database configurations and environment mappings. The documentation and tooling configuration files (CONTRIBUTING.md and pyproject.toml) have been updated to reflect the new support, with the minimum Python requirement raised from 3.8 to 3.9 and relevant classifiers adjusted.

Changes

File(s) Change Summary
.github/workflows/test.yml, tox.ini Removed Python 3.8 configurations and CI mappings; added Python 3.13 settings and updated database mappings and environment variables.
CONTRIBUTING.md, pyproject.toml Updated supported Python versions by removing Python 3.8 and adding Python 3.13; adjusted minimum version (from ≥3.8 to ≥3.9), classifiers, and tool-specific configurations.

Poem

In a garden of code where versions bloom anew,
I, a little rabbit, dance with a joyful view.
Python 3.8 bids farewell with a silent goodbye,
For 3.13 hops in under a bright sky.
With whiskers aglow and paws light on the ground,
I cheer the changes in every line found!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b3eada8 and b129735.

📒 Files selected for processing (1)
  • tox.ini (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • tox.ini

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@techouse techouse changed the title ⬆️ update Python version support to include 3.13 ⬆️ update Python version support to include 3.13 and drop 3.8 support Mar 12, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8d06619 and b3eada8.

📒 Files selected for processing (4)
  • .github/workflows/test.yml (15 hunks)
  • CONTRIBUTING.md (2 hunks)
  • pyproject.toml (4 hunks)
  • tox.ini (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (20)
  • GitHub Check: Test (python3.10, mysql:8.4, 0, true, 3.10)
  • GitHub Check: Test (python3.10, mysql:8.0, 0, false, 3.10)
  • GitHub Check: Test (python3.10, mysql:5.7, 0, false, 3.10)
  • GitHub Check: Test (python3.10, mysql:5.6, 1, false, 3.10)
  • GitHub Check: Test (python3.10, mysql:5.5, 1, false, 3.10)
  • GitHub Check: Test (python3.10, mariadb:11.4, 0, false, 3.10)
  • GitHub Check: Test (python3.11, mariadb:10.11, 0, false, 3.11)
  • GitHub Check: Test (python3.10, mariadb:10.11, 0, false, 3.10)
  • GitHub Check: Test (python3.10, mariadb:10.6, 0, false, 3.10)
  • GitHub Check: Test (python3.10, mariadb:10.5, 0, false, 3.10)
  • GitHub Check: Test (python3.10, mariadb:10.4, 0, false, 3.10)
  • GitHub Check: Test (python3.10, mariadb:10.3, 0, false, 3.10)
  • GitHub Check: Test (python3.11, mariadb:10.2, 0, false, 3.11)
  • GitHub Check: Test (python3.10, mariadb:10.2, 0, false, 3.10)
  • GitHub Check: Test (python3.11, mariadb:10.1, 1, false, 3.11)
  • GitHub Check: Test (python3.10, mariadb:10.1, 1, false, 3.10)
  • GitHub Check: Test (python3.11, mariadb:10.0, 1, false, 3.11)
  • GitHub Check: Test (python3.10, mariadb:10.0, 1, false, 3.10)
  • GitHub Check: Test (python3.10, mariadb:5.5, 1, false, 3.10)
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (8)
CONTRIBUTING.md (1)

16-17: Updated Supported Python Versions.
The contribution guidelines now correctly state that the tool supports Python versions 3.9, 3.10, 3.11, 3.12, and 3.13. This change is in line with the PR objectives. Please ensure that any other references to the older Python versions are updated accordingly.

tox.ini (1)

7-8: Addition of Python 3.13 to Environment List.
The envlist now includes python3.13, which correctly extends the support matrix in accordance with the project’s shift away from Python 3.8.

.github/workflows/test.yml (2)

63-68: Comprehensive Addition of Python 3.13 for MariaDB Configurations.
The workflow now incorporates Python 3.13 across all relevant MariaDB test environments (e.g. for mariadb:5.5, 10.0, 10.1, 10.2, 10.3, 10.4, 10.5, 10.6, and 10.11). This aligned inclusion is consistent with the new Python support. Please double-check that any downstream dependencies or scripts recognise the updated Python version string correctly.

Also applies to: 93-98, 123-128, 153-158, 183-188, 213-218, 243-248, 273-278, 303-308


393-398: Consistent Inclusion of Python 3.13 for MySQL Configurations.
The newly added Python 3.13 test environments for MySQL databases (including mysql:5.6, 5.7, 8.0, and 8.4) are well integrated into the testing matrix. Verify that the experimental flags and any other database-specific configurations continue to work as expected with Python 3.13.

Also applies to: 423-428, 452-457, 481-487

pyproject.toml (4)

10-10: Updated Minimum Python Requirement.
The requires-python field has been updated to ">=3.9" which is fully in accordance with the removal of Python 3.8 support.


36-36: Addition of Python 3.13 Classifier.
The inclusion of "Programming Language :: Python :: 3.13" in the classifiers now ensures that the project metadata accurately reflects the supported Python versions.


81-82: Updated Black Target Versions.
The target-version list under the [tool.black] section has been revised to include "py313" and remove "py38", which is perfectly aligned with the updated support for newer Python versions.


124-125: Updated MyPy Configuration.
The python_version under the [tool.mypy] section has been updated to "3.9", matching the new minimum Python version requirement.

Copy link

codecov bot commented Mar 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.15%. Comparing base (8d06619) to head (b129735).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #135   +/-   ##
=======================================
  Coverage   89.15%   89.15%           
=======================================
  Files           8        8           
  Lines         664      664           
=======================================
  Hits          592      592           
  Misses         72       72           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@techouse techouse merged commit 0a9c0b6 into master Mar 13, 2025
81 checks passed
@techouse techouse deleted the chore/drop-python-3.8-support branch March 13, 2025 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant