feat: Define "extra" optional dependencies with ml, starting with ins…

[Deependra-Patel]

…talling dataproc-ml

[gemini-code-assist]

Summary of Changes

Hello @Deependra-Patel, 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 enhances the project's dependency management by adding an optional ml dependency group. This allows users to selectively install machine learning-specific packages, starting with dataproc-ml, without burdening core installations with unnecessary dependencies. This modular approach improves flexibility and reduces the default installation footprint.

Highlights

• New Optional Dependency Group: An ml extra dependency group has been introduced in setup.py to manage machine learning-related packages.
• Dataproc ML Integration: The ml extra group now includes dataproc-ml as a dependency, with version constraints set between 1.0.0-rc1 and 1.0.

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

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 an 'ml' extra for optional dependencies, starting with dataproc-ml. While the addition is a good feature, the version specifier for dataproc-ml is overly restrictive. My feedback includes a suggestion to adjust the version constraint to allow for future patch releases, which will prevent potential dependency issues for users and allow them to receive bug fixes without requiring a new release of this package.

[gemini-code-assist]

The version specifier for dataproc-ml is very restrictive. The upper bound <=1.0 will prevent users from installing patch releases (e.g., 1.0.1) which may contain important bug fixes. It's better to allow for compatible future releases by specifying a more flexible upper bound for the version. Using <1.1 would allow for all 1.0.x releases, which is a common and recommended practice for libraries that follow semantic versioning.

Suggested change

	"ml": ["dataproc-ml>=1.0.0-rc1,<=1.0"],
	"ml": ["dataproc-ml>=1.0.0-rc1,<1.1"],