fix requirements

[helloyongyang]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @helloyongyang, 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 addresses the need to enhance the project's documentation capabilities by updating its build requirements. The changes introduce new Sphinx extensions that will allow for more sophisticated content rendering, such as mathematical equations and improved UI elements, making the documentation more comprehensive and user-friendly.

Highlights

• Documentation Dependencies: I've updated the documentation requirements by adding two new Sphinx extensions: sphinxcontrib-katex and sphinxcontrib.contentui. These additions will enable richer content display and advanced formatting within the project's documentation.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 adds two missing Sphinx dependencies, sphinxcontrib-katex and sphinxcontrib.contentui, to the documentation requirements. The change is necessary as these extensions are used in the Sphinx configuration files. My main feedback is to pin the versions of these new dependencies to ensure reproducible builds, which is a common best practice for managing dependencies. I've provided a suggestion to pin the newly added packages to their latest versions.

[gemini-code-assist]

For better reproducibility of the documentation build, it's a good practice to pin dependency versions. This prevents unexpected build failures when a new version of a dependency is released with breaking changes. I'd recommend pinning all dependencies in this file for consistency.

Specifically for this change, please pin the versions for the two new dependencies.

Additionally, for consistency with other packages in this file (e.g., sphinx-book-theme, myst-parser), it's conventional to use hyphens (-) instead of dots (.) in package names. While pip might handle them interchangeably, using the canonical name from PyPI improves clarity. Please use sphinxcontrib-contentui.

sphinxcontrib-katex == 0.9.0
sphinxcontrib-contentui == 0.2.0