feat: add modern PyPI publishing workflow with uv

[shaonianche]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @shaonianche, I'm Gemini Code Assist¹! 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 modernizes the project's Python packaging and build system by introducing a pyproject.toml file. This change centralizes project metadata, dependencies, and build configurations, making the project more compatible with contemporary Python tooling like uv for streamlined installation, building, and publishing to PyPI. It enhances maintainability and simplifies the development workflow for contributors and users alike.

Highlights

• Project Configuration Modernization: Introduced pyproject.toml to centralize project metadata, build system configuration, and dependencies, aligning with modern Python packaging standards (PEP 517/518).
• Dependency Management: Defined project dependencies (openpyxl, bitstruct) and Python version requirements (>=3.8) within pyproject.toml, streamlining dependency resolution.
• Build System Setup: Configured setuptools as the build backend, specifying setuptools>=61.0 and wheel as build requirements, which facilitates creating distributable packages.

🧠 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

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/publish.yml

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a pyproject.toml file to modernize the Python packaging setup, which is a great improvement. The new configuration file correctly captures most of the metadata from the old setup.py.

I've added a couple of suggestions to ensure a complete migration:

1. Restoring the zip_safe=False setting to prevent potential issues with zipped installations.
2. Migrating the test dependencies to project.optional-dependencies to maintain the development and testing workflow.

Additionally, I've noticed the license has been updated to BSD-3-Clause and the project URLs now point to GitHub. These are excellent changes for the project's health and community engagement.