Skip to content

Conversation

starbased-co
Copy link

Feel free to decline this, just making this to add it to the issue

Updated requires-python and tool configurations (black, ruff) to reflect
Python 3.10 as the new minimum supported version. Also added clink* to
package includes.
Copy link
Contributor

Summary of Changes

Hello @starbased-co, 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 primarily focuses on updating the project's Python environment and build configurations. It elevates the minimum required Python version to 3.10 and adjusts the black and ruff tooling to align with this new baseline. Additionally, it expands the project's package discovery to include a new clink module, ensuring it's properly recognized by the build system.

Highlights

  • Python Version Update: The minimum required Python version for the project has been updated from 3.9 to 3.10.
  • Package Discovery: The clink* module has been added to the setuptools package discovery configuration.
  • Tooling Configuration: The black and ruff formatting and linting tools have been configured to target Python 3.10, removing support for Python 3.9.
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
Contributor

@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 updates pyproject.toml to drop support for Python 3.9, requiring Python 3.10+ instead, and adds the new clink package to the project's packaging configuration. The changes to the required Python version and the configurations for tools like black and ruff are consistent with this goal.

My review focuses on two key aspects of these changes. First, dropping support for a Python version is a breaking change that should be reflected in the project's versioning, likely requiring a major version bump. Second, I've identified a potential issue where the setuptools configuration being used requires a newer version of setuptools than what is specified in the build-system requirements. Addressing these points will improve the project's release management and build reliability.

version = "7.1.0"
description = "AI-powered MCP server with multiple model providers"
requires-python = ">=3.9"
requires-python = ">=3.10"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

Changing the minimum required Python version from 3.9 to 3.10 is a breaking change for users on Python 3.9. According to semantic versioning principles, breaking changes should result in a major version bump (e.g., from 7.x.x to 8.0.0). Since this project uses semantic-release, please ensure the commit message for this change is formatted to indicate a breaking change, which will trigger the correct major version release.

Comment on lines 14 to +15
[tool.setuptools.packages.find]
include = ["tools*", "providers*", "systemprompts*", "utils*", "conf*"]
include = ["tools*", "providers*", "systemprompts*", "utils*", "conf*", "clink*"]
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The [tool.setuptools.packages.find] configuration table is used here to discover packages. This feature was introduced in setuptools version 61.0.0. However, the build-system.requires on line 118 only specifies setuptools>=45. This could lead to inconsistent or failed builds in environments with an older setuptools version (between 45 and 61). It's recommended to update the requirement to setuptools>=61.0.0 in build-system.requires to ensure predictable behavior.

@starbased-co
Copy link
Author

oi bugger off clanker

@guidedways
Copy link
Member

Thank you! Should be fixed in the latest update, please confirm!

@guidedways guidedways closed this Oct 6, 2025
@starbased-co
Copy link
Author

Thank you! Should be fixed in the latest update, please confirm!

confirm!

Sign up for free to 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