Skip to content

Explicitly support and test Python 3.13 #69

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Mar 20, 2025
Merged

Explicitly support and test Python 3.13 #69

merged 1 commit into from
Mar 20, 2025

Conversation

mrossinek
Copy link
Member

No description provided.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 13940860957

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%
Totals Coverage Status
Change from base Build 13681898423: 0.0%
Covered Lines: 432
Relevant Lines: 432
💛 - Coveralls

@mrossinek mrossinek marked this pull request as ready for review March 19, 2025 07:17
@mrossinek
Copy link
Member Author

Before merging this we will have to update the required checks in the branch protection rules

@mrossinek mrossinek added this to the 0.2 milestone Mar 19, 2025
garrison
garrison approved these changes Mar 19, 2025
View reviewed changes
Copy link
Member

@garrison garrison left a comment

Choose a reason for hiding this comment

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

Looks great

@mrossinek mrossinek merged commit 98ae544 into main Mar 20, 2025
16 checks passed
@mrossinek mrossinek deleted the python-3.13 branch March 20, 2025 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@garrison garrison garrison approved these changes

@caleb-johnson caleb-johnson Awaiting requested review from caleb-johnson

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.2
Development

Successfully merging this pull request may close these issues.
3 participants
@mrossinek @coveralls @garrison