chore(migration): Migrate code from googleapis/proto-plus-python into packages/proto-plus

[parthea]

See #14906.

This PR should be merged with a merge-commit, not a squash-commit, in order to preserve the git history.

[gemini-code-assist]

Summary of Changes

Hello @parthea, 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 completes the migration of the proto-plus-python library into a monorepo structure. The primary goal was to relocate all existing code and its complete git history to a new subdirectory, packages/proto-plus, ensuring a seamless transition and maintainability within the larger repository.

Highlights

• Library Migration: The entire proto-plus-python library has been migrated into the packages/proto-plus directory within this repository.
• Git History Preservation: The migration process was designed to preserve the full git history of the proto-plus-python library, requiring a merge-commit rather than a squash-commit.
• Comprehensive File Relocation: All source code, documentation, configuration files, and tests from the original repository have been moved to their new location under packages/proto-plus.
• Migration Script Enhancements: The single-library.git-migrate-history.sh script was updated to correctly handle submodules and remove .git directories during the migration process.

Changelog

• packages/proto-plus/CHANGELOG.md
  • Removed float_precision for protobuf 7 compatibility in version 1.27.1.
  • Added classifier for Python 3.14 support in version 1.27.0.
  • Allowed protobuf 6.x in version 1.26.1.
  • Migrated to pyproject.toml and fixed various protobuf compatibility issues in version 1.26.0.
  • Added support for Python 3.13 in version 1.25.0.

Activity

• This PR addresses issue Adopt split repo: _proto-plus-python_ #14906.
• The author explicitly requested a merge-commit to preserve git history.

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 migrates the proto-plus library into the monorepo structure. The migration is comprehensive, including source code, documentation, and a full test suite. I have identified several critical issues in the GitHub Actions workflow configuration where non-existent versions of standard actions are being referenced, which will cause CI failures. Additionally, there are minor maintainability improvements such as removing unused imports and unused variables in exception handlers. The core logic for handling Protobuf version differences (especially the breaking changes in Protobuf 5.0.0 and 7.x) appears to be correctly implemented and preserved during the migration. No comments were dropped or modified based on the provided rules, as they did not apply to the identified issues.

I am having trouble creating individual review comments. Click here to see my feedback.

packages/proto-plus/.github/workflows/tests.yml (20)

The version v6 for actions/checkout does not exist. The current stable version is v4.

      - uses: actions/checkout@v4

packages/proto-plus/.github/workflows/tests.yml (22)

The version v6 for actions/setup-python does not exist. The current stable version is v5.

      - name: Set up Python 3.8
        uses: actions/setup-python@v5

packages/proto-plus/.github/workflows/tests.yml (88)

The version v6 for actions/upload-artifact does not exist. The current stable version is v4.

      - name: Upload coverage results
        uses: actions/upload-artifact@v4

packages/proto-plus/.github/workflows/tests.yml (134)

The version v7 for actions/download-artifact does not exist. The current stable version is v4.

    - name: Download coverage results
      uses: actions/download-artifact@v4

packages/proto-plus/proto/datetime_helpers.py (17)

The calendar module is imported but not used in this file.

import datetime

packages/proto-plus/proto/marshal/rules/dates.py (17)

The timezone import from datetime is unused in this module.

from datetime import timedelta

packages/proto-plus/proto/marshal/rules/message.py (37)

The exception variable ex is defined but never used in the catch block.

            except (TypeError, ValueError, AttributeError):

[parthea]

This PR is ready for review but not merge