Modernize entrypoints module with type hints and use generic types

[sugatmahanti]

SUMMARY:
This is part of #1927

Modernize type annotations using | operator and built-in generics in the entrypoints module as part of codebase modernization effort. I also fixed 2 typos as part of this PR.

TEST PLAN:

• make style
• make quality
• make tests

Notes:
Happy to address any comments! Also please let me know if you dont want typos to be fixed as part of this PR. Thank you!

[gemini-code-assist]

Summary of Changes

Hello @sugatmahanti, 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 modernizes the type annotations within the entrypoint module, adopting the contemporary Python 3.10+ syntax for union types and built-in generics. This change enhances code readability and maintainability by simplifying type declarations, contributing to an ongoing codebase modernization effort. Additionally, it includes minor corrections for two typographical errors.

Highlights

• Modernized Type Annotations: Updated type hints across the entrypoint module to use the more concise | operator for union types and built-in generic types (e.g., list, dict) instead of typing.Union, typing.Optional, typing.List, typing.Dict. This aligns with Python 3.10+ syntax.
• Removed Redundant Imports: Eliminated imports for Dict, List, Optional, and Union from the typing module as they are no longer needed with the modernized syntax.
• Typo Corrections: Fixed two minor typos in comments and docstrings for improved clarity and accuracy.

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

[github-actions]

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

[gemini-code-assist]

Code Review

This pull request modernizes the type annotations in the entrypoint modules by using the | operator for unions and built-in generic types like list and dict. The changes are well-executed and improve code readability. I've also noted the typo fixes, which are appreciated. My review includes a couple of suggestions to further improve consistency and clarity, mainly related to ensuring type hints are specific and that docstrings are updated to match the new type hints.