chore(ci,docs): align Python to 3.11 and update docs — Resolves #1961#1962
chore(ci,docs): align Python to 3.11 and update docs — Resolves #1961#1962Anselmoo wants to merge 1 commit intokeras-team:masterfrom
Conversation
- Update CI, container images, and docs to match pyproject (Python >= 3.11). - Note: will follow up to update ipynb metadata. - Fixes keras-team#1961
Summary of ChangesHello @Anselmoo, 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 standardizes the Python version across the project to 3.11, aligning the development environment, CI/CD pipelines, and documentation with the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Ignored Files
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request effectively aligns the project with Python 3.11 by updating the required version in pyproject.toml, Dockerfiles, and documentation. The changes are consistent across the repository. I've added a couple of minor suggestions to improve code style in pyproject.toml and formatting in README.md.
| ## | ||
|
|
| "Programming Language :: Python :: 3", | ||
| "Programming Language :: Python :: 3.11", | ||
| "Programming Language :: Python :: 3.12", | ||
| "Programming Language :: Python :: 3 :: Only", |
There was a problem hiding this comment.
For better readability and to maintain consistency, it's a good practice to sort the classifiers alphabetically. This makes it easier to see which Python versions are supported at a glance.
| "Programming Language :: Python :: 3", | |
| "Programming Language :: Python :: 3.11", | |
| "Programming Language :: Python :: 3.12", | |
| "Programming Language :: Python :: 3 :: Only", | |
| "Programming Language :: Python :: 3", | |
| "Programming Language :: Python :: 3 :: Only", | |
| "Programming Language :: Python :: 3.11", | |
| "Programming Language :: Python :: 3.12", |
Which issue(s) does this Pull Request fix?
resolves #1961
Summary
Align CI, container images, and documentation with
pyproject.toml(Python >= 3.11). This also includes documentation updates and a follow-up note to update ipynb metadata.Details of the Pull Request
.devcontainer/Dockerfile.github/workflows/actions.ymlREADME.mddocker/pre-commit.Dockerfiledocs/tutobooks.pypyproject.tomlpyproject.tomlrequires Python >= 3.11; aligning CI and container images prevents version mismatch and ensures consistent build/test environments.Documentation & Notes
Checklist