refactor(py/samples): use a central script to run samples

[yesudeep]

[gemini-code-assist]

Summary of Changes

Hello @yesudeep, 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 significantly refactors the Python samples directory by standardizing how samples are run and organized. The core change involves introducing a central run_sample script, creating individual run.sh scripts for each sample, and renaming the main Python entry point in each sample to main.py. These changes aim to streamline the developer experience by providing a consistent and simplified way to execute and interact with the various Python samples.

Highlights

• Centralized Sample Runner: A new bash script, py/bin/run_sample, has been introduced to provide a unified way to execute all Python samples. This script can optionally use gum for interactive sample selection.
• Standardized Sample Execution: Each Python sample now includes a run.sh script in its root directory, which encapsulates the specific commands needed to run that sample. This simplifies sample execution and improves consistency.
• Main File Renaming: The primary Python source file within each sample's src/ directory has been consistently renamed to main.py (e.g., anthropic_hello.py is now main.py).
• Documentation Updates: All README.md files across the Python samples have been updated to reflect the new run.sh execution method and the main.py file naming convention.
• Litestar Typing Fix: A minor but important fix was applied in py/packages/genkit/src/genkit/web/typing.py to correctly import litestar.types, ensuring proper type hinting for ASGI applications.

🧠 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 a significant and useful refactoring by creating a centralized script, py/bin/run_sample, to execute the Python samples. This standardizes the process of running samples and simplifies the developer experience. The changes involve adding run.sh scripts to each sample, renaming main files to src/main.py, and updating documentation accordingly.

The new run_sample script is well-structured, but I have a couple of suggestions to improve its robustness and user experience. Specifically, I've commented on improving the sample discovery logic and making the automatic installation of gum less intrusive.

Overall, this is a great improvement for the project's sample ecosystem.