Remove setup_request_id fallback in generated packages when google-api-core >= 2.26.0

Open
  • Is something wrong?
#17,813 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@hebaalazzeh is already working on this.

Since Jul 21, 2026.

Assessment

This issue has not been assessed yet.

Description

Overview

During the GAPIC request-id deduplication effort (centralizing request ID generation into google.api_core.gapic_v1.requests.setup_request_id), a backward-compatibility fallback module (_compat.py) was introduced in generated client packages to maintain compatibility with older versions of google-api-core.

Once google-api-core >= 2.26.0 (or the version containing setup_request_id) becomes the minimum required version across all generated client packages, this fallback can be removed.

Tasks

  • Remove _compat.py.j2 template from gapic-generator-python.
  • Update client.py.j2 and async_client.py.j2 to import setup_request_id directly from google.api_core.gapic_v1.requests.
  • Remove _compat.py files from tests/integration/goldens/.
Dominant language
Python
Stars
5.4k
Forks
1.8k
Avg merge
2d 7h
Merged PRs (30d)
173

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-cloud-python

All issues in googleapis/google-cloud-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.