Skip to content

Conversation

@parthea
Copy link
Contributor

@parthea parthea commented Jan 22, 2026

Fixes #208

@parthea parthea requested review from a team as code owners January 22, 2026 19:05
@product-auto-label product-auto-label bot added the size: xs Pull request size is extra small. label Jan 22, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello @parthea, 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 addresses an issue where pytest was emitting FutureWarning messages concerning deprecated Python versions. By updating the pytest.ini configuration, these specific warnings are now filtered out, leading to cleaner and more focused test output. This change improves the signal-to-noise ratio in test runs, making it easier to identify relevant test failures or warnings rather than deprecation notices.

Highlights

  • Test Configuration Update: Added new ignore rules to pytest.ini to suppress FutureWarning messages that are related to using Python versions past their end-of-life.
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.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

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 aims to filter warnings related to deprecated Python versions by adding new rules to pytest.ini. While the intent is correct, the regular expressions used for filtering are overly broad and could lead to unintentionally suppressing other warnings. I've provided a suggestion to make the patterns more specific and robust, ensuring they only match the intended warnings.

Comment on lines +7 to +8
ignore:.*Please upgrade to the latest Python version.*:FutureWarning
ignore:(?s).*using a Python version.*past its end of life.*:FutureWarning

Choose a reason for hiding this comment

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

medium

These regular expressions can be made more specific to improve clarity and prevent unintentionally matching other warnings. The filterwarnings option matches patterns from the start of the warning message.

  1. The pattern .*Please upgrade to the latest Python version.* is too broad and will match both warnings you are trying to filter, making the second filter redundant.
  2. The pattern (?s).*using a Python version.*past its end of life.* is also broad, and the (?s) flag is unnecessary for single-line warnings.

Using more specific patterns anchored to the beginning of each warning message is a more robust approach.

    ignore:Please upgrade to the latest Python version:FutureWarning
    ignore:You are using a Python version that is past its end of life.*:FutureWarning

@parthea parthea enabled auto-merge (squash) January 22, 2026 20:15
@parthea parthea merged commit b0056c3 into main Jan 22, 2026
17 checks passed
@parthea parthea deleted the parthea-patch-1 branch January 22, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The build failed

3 participants