Skip to content

Conversation

@shimizust
Copy link
Collaborator

Motivation

Modifications

  • Added version.txt to MANIFEST.in so can build wheel correctly
  • Fixes this error when running python -m build:
  File "<string>", line 16, in read_version
FileNotFoundError: [Errno 2] No such file or directory: 'version.txt'

ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @shimizust, 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 a critical issue preventing the successful build and distribution of the package. It rectifies a FileNotFoundError by ensuring that the version.txt file, which was previously missing from the distribution, is now properly included in the package manifest. This change allows the build process to complete without errors, facilitating correct package creation.

Highlights

  • Build Fix: Resolves a FileNotFoundError that occurred when attempting to build the package, specifically when python -m build was executed.
  • Package Distribution: Ensures that the version.txt file is correctly included in the package distribution by adding it to MANIFEST.in.
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 correctly addresses a FileNotFoundError during the package build process by including version.txt in the source distribution via MANIFEST.in. The change is effective and directly solves the issue. I have included one suggestion to make the MANIFEST.in file more generic and potentially easier to maintain in the future.

@FrankLeeeee
Copy link
Collaborator

Thanks!

@FrankLeeeee FrankLeeeee merged commit a05d76e into sgl-project:main Oct 14, 2025
2 checks passed
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