[Question] Clarification on the relationship between zai-sdk and zhipuai: differences, maintenance status, and renaming rationale #55
Description
Hello Zhipu AI team and maintainers,
First, thank you for providing SDKs for the developer community. I've been using the official Python SDK zhipuai and recently noticed the release of a new SDK named zai-sdk.
To help with migration and future development planning, I would like to ask for clarification on the following points:
Key Differences: What are the main technical and functional differences between the older zhipuai and the new zai-sdk? (e.g., API coverage, interface design, dependency management, or supported features).
Maintenance & Migration Path:
Is the zhipuai now considered deprecated or in maintenance mode, with zai-sdk being its official successor/replacement?
If zai-sdk is indeed the replacement, what is the rationale behind creating a new project with a different name (zai-sdk) rather than continuing to develop under the well-established zhipuai name? (e.g., major breaking changes, a complete redesign, or a new project scope).
Is there an official migration guide or recommended path for projects currently using zhipuai to transition to zai-sdk?
Having this information in the repository's README or documentation would be incredibly helpful for all developers evaluating or using your SDKs.
Thank you for your time and clarification.