-
Notifications
You must be signed in to change notification settings - Fork 54
Remove deprecated entries from setup.cfg #288
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.
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
base: main
Are you sure you want to change the base?
Conversation
License classifiers are deprecated in favor of SPDX license expressions. With Python 2.7 end-of-life, support for building universal wheels is being removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @cjmayo, 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 streamlines the setup.cfg
configuration by removing outdated entries. It updates the license classification to align with modern standards that favor SPDX license expressions and removes the configuration for building universal wheels, a feature no longer supported following the end-of-life of Python 2.7. These changes ensure the project's packaging metadata is current and efficient.
Highlights
- License Classifier Update: Removed the deprecated "License :: OSI Approved :: MIT License" classifier from
setup.cfg
as SPDX license expressions are now the preferred method for specifying licenses. - Universal Wheel Build Removal: Eliminated the
[bdist_wheel]
section and itsuniversal = 1
setting fromsetup.cfg
. This change reflects the removal of support for building universal wheels, which is a consequence of Python 2.7 reaching its 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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
-
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. ↩
There was a problem hiding this 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 correctly removes deprecated entries from setup.cfg
. The removal of the License :: OSI Approved :: MIT License
classifier is appropriate as it's superseded by the license = MIT
SPDX identifier. Similarly, removing the [bdist_wheel]
section with universal = 1
is correct given that Python 2 support is no longer necessary. These changes are good housekeeping and align the project with current Python packaging standards.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any tools that throw a warning because of these deprecated lines? if not, i dont see why we would remove it.
Yes:
|
License classifiers are deprecated in favor of SPDX license expressions.
With Python 2.7 end-of-life, support for building universal wheels is being removed.