tests: skip mypy for packages without py.typed

[parthea]

See follow up issue #13362

[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 integrates mypy type checking sessions into the Nox configurations across multiple Python packages. The sessions are currently set to be skipped for packages lacking a py.typed marker, acknowledging a known issue and ensuring that type checking can be progressively enabled without immediate failures. This change prepares the repositories for more robust type safety in the future.

Highlights

• Mypy Session Introduction: A new mypy Nox session has been added to the noxfile.py for several packages, laying the groundwork for future type checking.
• Conditional Mypy Skipping: The newly introduced mypy sessions are configured to be skipped for packages that do not yet include a py.typed marker, with a reference to issue Include mypy types / add py.typed #13362 for tracking the eventual enablement.

Changelog

• packages/google-cloud-access-context-manager/noxfile.py
  • Added a mypy Nox session.
  • Configured the mypy session to skip execution with a comment referencing issue Include mypy types / add py.typed #13362.
• packages/google-cloud-audit-log/noxfile.py
  • Added a mypy Nox session.
  • Configured the mypy session to skip execution with a comment referencing issue Include mypy types / add py.typed #13362.
• packages/googleapis-common-protos/noxfile.py
  • Added a mypy Nox session.
  • Configured the mypy session to skip execution with a comment referencing issue Include mypy types / add py.typed #13362.
• packages/grpc-google-iam-v1/noxfile.py
  • Added a mypy Nox session.
  • Configured the mypy session to skip execution with a comment referencing issue Include mypy types / add py.typed #13362.

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 skips the mypy check for four packages that do not have a py.typed file, implemented consistently across the modified noxfile.py files as a temporary measure. No obvious security vulnerabilities such as injection or hardcoded secrets were identified. A minor improvement has been suggested for the TODO comment in each noxfile.py file to make it more specific about re-enabling mypy.

[gemini-code-assist]

The comment 'Enable mypy once this bug is fixed' is a bit vague. It would be clearer to state what needs to be done to enable mypy for this package. Consider rephrasing to clarify that a py.typed file is needed.

Suggested change

	# Enable mypy once this bug is fixed.
	# Enable mypy once this package has a py.typed file.

[gemini-code-assist]

The comment 'Enable mypy once this bug is fixed' is a bit vague. It would be clearer to state what needs to be done to enable mypy for this package. Consider rephrasing to clarify that a py.typed file is needed.

Suggested change

	# Enable mypy once this bug is fixed.
	# Enable mypy once this package has a py.typed file.

[gemini-code-assist]

The comment 'Enable mypy once this bug is fixed' is a bit vague. It would be clearer to state what needs to be done to enable mypy for this package. Consider rephrasing to clarify that a py.typed file is needed.

Suggested change

	# Enable mypy once this bug is fixed.
	# Enable mypy once this package has a py.typed file.

[gemini-code-assist]

The comment 'Enable mypy once this bug is fixed' is a bit vague. It would be clearer to state what needs to be done to enable mypy for this package. Consider rephrasing to clarify that a py.typed file is needed.

Suggested change

	# Enable mypy once this bug is fixed.
	# Enable mypy once this package has a py.typed file.