Skip to content

chore: update pytest to v9 - #559

Merged
gruebel merged 2 commits into
mainfrom
update-pytest
Jan 20, 2026
Merged

chore: update pytest to v9#559
gruebel merged 2 commits into
mainfrom
update-pytest

Conversation

@gruebel

Copy link
Copy Markdown
Member

This PR

  • the new pytest version only support Python 3.10+ and now properly supports pyproject.toml configs
  • also it has now a strict mode, which checks for some typical misconfigurations, like missing marker setup

Signed-off-by: gruebel <anton.gruebel@gmail.com>
@gruebel
gruebel requested review from a team as code ownersJanuary 9, 2026 22:43
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @gruebel, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a significant upgrade of the pytest testing framework to its latest major version (v9), along with its associated pytest-asyncio plugin. This update modernizes the test suite's infrastructure by leveraging improved pyproject.toml configuration support and activating a new strict mode to enhance test reliability. A key change is the new requirement for Python 3.10 or newer. Additionally, various other development dependencies have been updated to ensure overall system compatibility and benefit from the latest features and fixes.

Highlights

  • Pytest Upgrade: The pytest testing framework has been updated to version 9.0.0 or higher, which now requires Python 3.10+.
  • Pytest-Asyncio Upgrade: The pytest-asyncio plugin has been updated to version 1.3.0 or higher to maintain compatibility with the new pytest version.
  • Pyproject.toml Configuration: Pytest configuration has been migrated to the [tool.pytest] section in pyproject.toml, improving adherence to modern Python project standards.
  • Strict Mode Enabled: The strict mode for pytest has been enabled, which will help identify and prevent common test misconfigurations.
  • Dependency Updates: Several other development dependencies managed by uv.lock have been updated to their latest versions.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request successfully updates pytest to version 9. The changes correctly migrate the configuration in pyproject.toml from [tool.pytest.ini_options] to the modern [tool.pytest] section, and enables the new strict mode, which is a good practice. The dependencies for pytest and pytest-asyncio are now appropriately version-constrained. The uv.lock file is also updated to reflect these changes. Overall, this is a solid dependency update.

@codecov

codecovBot commented Jan 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.01%. Comparing base (9fc6121) to head (37ed54e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #559 +/- ##
=======================================
Coverage 98.01% 98.01% =======================================
Files 41 41 Lines 1913 1913 =======================================
Hits 1875 1875 Misses 38 38 
FlagCoverage Δ
unittests98.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

@aepfliaepfli left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

thank you - improving our tool is always a good idea

@gruebel
gruebel merged commit 71ebb9f into mainJan 20, 2026
15 checks passed
@gruebel
gruebel deleted the update-pytest branch January 20, 2026 18:26
Sign up for freeto 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.

2 participants

@gruebel@aepfli