Update Get_started_LiveAPI.py

[for-the-zero]

The file is outdated
I copied the code from aistudio.google.com/live but it's alse outdated, it used some deprecated methods
So I modified this it so that it could run expectedly

[gemini-code-assist]

Summary of Changes

Hello @for-the-zero, 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 updates the Get_started_LiveAPI.py quickstart script to ensure compatibility with the latest version of the google.genai library's Live API. The changes address deprecated methods, upgrade the underlying Gemini model to a newer preview version, and introduce more comprehensive configuration options for live connections, making the example functional and aligned with current best practices.

Highlights

• API Method Updates: The methods for sending both text and real-time media input have been updated from self.session.send to self.session.send_client_content and self.session.send_realtime_input respectively, reflecting changes in the google.genai library's Live API.
• Model Upgrade: The script now utilizes the gemini-live-2.5-flash-preview model, upgrading from the previous gemini-2.0-flash-live-001.
• Enhanced LiveConnect Configuration: The CONFIG object has been significantly expanded to use types.LiveConnectConfig, allowing for more granular control over response modalities, media resolution, speech configuration (including voice selection like 'Zephyr'), and context window compression.
• API Key Integration: The genai.Client initialization now explicitly includes an api_key parameter, retrieving it from the GEMINI_API_KEY environment variable for better security and flexibility.
• Python Version Compatibility: Removed explicit taskgroup and exceptiongroup imports, suggesting an assumption of Python 3.11+ where asyncio.TaskGroup and asyncio.ExceptionGroup are standard library features.

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 updates Get_started_LiveAPI.py to use the latest methods from the google-genai SDK, replacing deprecated calls. The changes look good and align with the goal of modernizing the script. I've found one issue regarding an inconsistency in the environment variable used for the API key, which could confuse users. Please see my specific comment for details. Otherwise, the updates to the model, client configuration, and API calls are well-implemented.