Skip to content

Conversation

@zimeg
Copy link
Member

@zimeg zimeg commented Jul 14, 2025

Summary

This PR adds support for Python 3.13 🐍 ✨

Reference

Requirements

  • I've read and understood the Contributing Guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've run ./scripts/install_and_run_tests.sh after making the changes.

@zimeg zimeg requested review from WilliamBergamin and ewanek1 July 14, 2025 23:06
@zimeg zimeg self-assigned this Jul 14, 2025
@zimeg zimeg added enhancement New feature or request dependencies Pull requests that update a dependency file semver:minor labels Jul 14, 2025
@codecov
Copy link

codecov bot commented Jul 14, 2025

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 94.68%. Comparing base (0bcc92b) to head (0d9a006).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #61   +/-   ##
=======================================
  Coverage   94.68%   94.68%           
=======================================
  Files          11       11           
  Lines         207      207           
=======================================
  Hits          196      196           
  Misses         11       11           

β˜” 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.

Copy link
Member

@mwbrooks mwbrooks left a comment

Choose a reason for hiding this comment

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

βœ… Thanks a lot @zimeg!

❓ Is there any automation that we can use to keep this up-to-date?

@zimeg
Copy link
Member Author

zimeg commented Jul 14, 2025

@mwbrooks I do hope so, but I'm not aware of such at this time πŸ‘Ύ

Poking into this topic, I'm not sure if these new versions bring breaking changes alongside deprecations of the last version though:

Python versions are numbered β€œA.B.C” or β€œA.B”:

  • A is the major version number – it is only incremented for really major changes in the language.
  • B is the minor version number – it is incremented for less earth-shattering changes.
  • C is the micro version number – it is incremented for each bugfix release.

πŸ”— https://docs.python.org/3/faq/general.html#how-does-the-python-version-numbering-scheme-work

That might sometimes require us to make changes, but I'm optimistic we can soon remain with the current supported versions overall.

I agree that if automations do appear it would be nice to use these!

Copy link

@ewanek1 ewanek1 left a comment

Choose a reason for hiding this comment

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

Looks good to me! ☺ ☺

It seems like some developers have run into similar tedious tasks of manually updating version numbers and created tools to automate it.

Copy link
Contributor

@WilliamBergamin WilliamBergamin left a comment

Choose a reason for hiding this comment

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

Thanks for working on this πŸ’―

@zimeg
Copy link
Member Author

zimeg commented Jul 15, 2025

It seems like some developers have run into similar tedious tasks of manually updating version numbers and created tools to automate it.

@ewanek1 This is so interesting to me! The author seems to be using a standalone script to make these updates and I'm now both curious and optimistic that we might later adapt something similar to these codebases.

I find custom workflows can be so useful, but can also be time consuming to set up. The xkcd related echoes in mind! 🧠 πŸ’¨

I'll merge this as is but am keeping watch for these improvements since I believe ongoing maintenance should be little effort. Also, thank you for sharing this!

@mwbrooks @ewanek1 @WilliamBergamin I appreciate the kind reviews. I will merge this and am also interested in a release soon after, but will save that discussion for another PR! 🚒

@zimeg zimeg merged commit b918d8d into main Jul 15, 2025
17 checks passed
@zimeg zimeg deleted the zimeg-chore-python-3.13 branch July 15, 2025 20:00
@zimeg zimeg added this to the 0.1.0 milestone Jul 15, 2025
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 enhancement New feature or request semver:minor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants