Provide versioned PyPI releases for wespeaker instead of Git-based installation

[gooran]

Currently, wespeaker is primarily installed via a Git URL, for example:

pip install git+https://github.com/wenet-e2e/wespeaker.git

While this works for development, it introduces several practical issues for users and downstream projects: lack of version pinning, reduced reproducibility, harder dependency management, and complications in production deployments and CI/CD pipelines. Installing directly from a Git repository also bypasses standard Python packaging workflows and release guarantees.

It would be beneficial to provide proper, versioned releases of wespeaker (e.g., via PyPI) so users can install it in a standard and reproducible way, such as:

pip install wespeaker==0.0.1

Proposed solution:

• Add/complete Python packaging metadata (pyproject.toml or setup.py) following modern packaging standards.
• Define and tag semantic versions (e.g., v0.0.1, v0.1.0).
• Publish release artifacts to PyPI.
• Optionally document the release and installation process in the README.

This would significantly improve usability, stability, and adoption of wespeaker, especially for production and research environments that rely on strict dependency control.

[hjj-lmx]

目前，wespeaker 主要通过 Git URL 安装，例如：

pip install git+https://github.com/wenet-e2e/wespeaker.git

虽然这种方式对开发环境有利，但它会给用户和下游项目带来一些实际问题：版本锁定缺失、可复现性降低、依赖管理更加复杂，以及生产部署和 CI/CD 流水线的复杂性。直接从 Git 仓库安装还会绕过标准的 Python 打包工作流程和发布保证。

如果能提供版本明确的 wespeaker 发行版（例如通过 PyPI），用户就可以以标准且可复现的方式安装它，例如：

pip install wespeaker==0.0.1

建议的解决方案：

• 按照现代打包标准添加/完善 Python 打包元数据（pyproject.toml或）。setup.py
• 定义并标记语义版本（例如v0.0.1，，v0.1.0）。
• 将发布版本发布到 PyPI。
• （可选）在 README 文件中记录发布和安装过程。

这将显著提高 wespeaker 的可用性、稳定性和普及度，尤其适用于依赖严格依赖关系控制的生产和研究环境。

有找到更好的方案吗？整个环境感觉好老