doc: Final tweaks on Python Packaging

[junrushao]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @junrushao, 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 refines the documentation related to Python packaging and ABI concepts. It enhances the clarity of the ABI overview by updating its title and provides crucial guidance on how to access global functions across different languages within the TVM FFI framework. Additionally, a small organizational tweak was made to an example C++ file to improve code readability.

Highlights

• Documentation Clarity: The main heading in the ABI overview document has been updated from 'ABI Specification' to 'ABI Overview' for better clarity and conciseness.
• Python Packaging Guidance: New documentation has been added to explain how to retrieve global functions in Python, C, and C++ within the TVM FFI context, complete with a Python code example.
• Example Code Refinement: A minor adjustment was made in the extension.cc example file to reposition a comment, improving the logical grouping of the global function example.

🧠 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 provides some final tweaks to the Python packaging documentation. The changes are mostly good, clarifying how to retrieve global functions and adjusting the title of the ABI overview. However, there are a couple of minor issues. One is a small correction in a reStructuredText cross-reference. The other is a change to an example file that makes the documentation inconsistent. My review includes suggestions to address these points.

[gemini-code-assist]

By moving // [global_function.end] here, the code snippet included in the documentation no longer shows the registration of the AddOne function using tvm::ffi::reflection::GlobalDef. This makes the accompanying text in docs/packaging/python_packaging.rst confusing, as it specifically describes this registration process. For consistency with other examples in the document (like the Class example which shows both definition and registration), it would be better to include the registration block. Please consider reverting this change and the corresponding removal of the tag at the end of the TVM_FFI_STATIC_INIT_BLOCK.