chore(migration): Migrate code from googleapis/python-bigquery-pandas into packages/pandas-gbq

[ohmayr]

See #10988.

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, 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 focuses on migrating the pandas-gbq code from the googleapis/python-bigquery-pandas repository into a dedicated packages/pandas-gbq directory within the google-cloud-python repository. This involves adding various configuration files, documentation, tests, and benchmark scripts to ensure the package functions correctly in its new location. The goal is to improve code organization and maintainability.

Highlights

• Code Migration: Migrated code from the googleapis/python-bigquery-pandas repository into the packages/pandas-gbq directory to consolidate the codebase.
• File Additions: Added numerous configuration and metadata files to the packages/pandas-gbq directory, including .coveragerc, .flake8, .gitattributes, .gitignore, .librarian/state.yaml, .pre-commit-config.yaml, .readthedocs.yml, .repo-metadata.json, AUTHORS.md, and SECURITY.md.
• Changelog and Documentation: Added a comprehensive CHANGELOG.md file and documentation-related files (CONTRIBUTING.rst, LICENSE.txt, README.rst, ROADMAP.md) to the new packages/pandas-gbq directory.
• Benchmark and Test Setup: Included benchmark scripts and testing-related files, such as a .gitignore in the testing directory, constraints files, and unit/system test configurations.

Changelog

• packages/pandas-gbq/CHANGELOG.md
  • Added a comprehensive changelog for the pandas-gbq package, detailing version history, features, bug fixes, and dependency changes.

Activity

• The pull request involves a significant reorganization of the codebase, moving it from one repository to another.
• The author has requested that the PR be merged using 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 python-bigquery-pandas library into a new package structure. The changes involve adding a significant number of files, including the library's source code, tests, documentation, and various configuration files for CI/CD and development tooling. My review focused on ensuring these new files are correctly configured and adhere to best practices. I've identified a few issues, primarily concerning file formatting and configuration validity, which could affect builds and tooling. The feedback provided aims to correct these to ensure a smooth integration.

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

packages/pandas-gbq/.readthedocs.yml (22)

The version key is duplicated at the top level of this YAML file, which is invalid. This will cause the documentation build on Read the Docs to fail. Please remove the duplicate key.

packages/pandas-gbq/docs/conf.py (40)

The __version__ is not being set correctly; it will be an empty string. This will cause the documentation to display an incorrect version. You should import the version from the package to ensure it's always up-to-date.

from pandas_gbq import __version__

packages/pandas-gbq/.github/header-checker-lint.yml (15)

This JSON file is missing a final newline character. It's a good practice to end files with a newline for POSIX compatibility and to avoid issues with some tools.

}

packages/pandas-gbq/.kokoro/trampoline.sh (28)

This script is missing a final newline character. It's a good practice to end script files with a newline for POSIX compatibility.

python3 "${KOKORO_GFILE_DIR}/trampoline_v1.py"

packages/pandas-gbq/requirements.txt (5)

This file is missing a final newline character. It's a good practice to end files with a newline for POSIX compatibility and to avoid issues with some tools.

tqdm

packages/pandas-gbq/tests/data/dummy_key.json (5)

This JSON file is missing a final newline character. It's a good practice to end files with a newline for POSIX compatibility and to avoid issues with some tools.

    }