This release is a pre-release and may not be stable for production use.
qatlas-cli — QuantumAtlas 的命令行客户端
独立的 qatlas 客户端,通过 HTTP 与 qatlasd 交互,提供论文获取、贡献上传和本地解析等工作流;本仓不含服务端代码。
安装
推荐使用隔离的全局工具环境(Python 3.11+):
uv tool install qatlas-cli
qatlas --help
旧 quantum-atlas 工具用户先执行 uv tool uninstall quantum-atlas,再安装新包;已有配置和 PAT 保留。
其他安装方式、命令与插件协议、兼容性、配置、开发测试和发布规则见 完整项目概览。
文档
文档目录使用原生 Sphinx + MyST + Furo;完整正文只维护在 docs/,不在 README 重复维护。
文档构建独立于 pyproject.toml / uv.lock,不安装应用、插件或 GPU 依赖。
从仓库根目录执行(Python 3.12、uv 0.11.30):
uv run --locked --script docs/build.py
产物为 build/docs/index.html,只在本地生成,不自动发布。
独立的 .github/workflows/docs.yml 对默认分支 push/PR 的 README、docs 和该 workflow 变更执行同样的严格构建与校验,也支持手动运行;不发布网站、镜像或应用版本。
文档依赖写在 docs/build.py 的 PEP 723 头,锁为 docs/build.py.lock。
Sphinx 暂固定 8.2.3,以避开 9.1.0 已确认的中文搜索回归;不对搜索实现打补丁。
有意更新文档依赖时,改脚本头并用同一 uv 版本重新锁:
uv lock --script docs/build.py
开发与发版
开发、测试、兼容协议与完整发版步骤见 项目概览。版本由锁定的 Commitizen(uv provider)从 pyproject.toml 写入 PEP 440 号(如 0.34.1rc1):先 cz bump --dry-run,授权后再 bump 并推送 annotated tag,CI 发 PyPI 与 GitHub Release。本仓不用 GoReleaser;服务端发版在 QuantumAtlas。
Metadata
Release files for qatlas-cli 0.38.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| qatlas_cli-0.38.0rc1.tar.gz | 286.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qatlas_cli-0.38.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 414.7 kB
Release files / qatlas_cli-0.38.0rc1.tar.gz
| Download URL | qatlas_cli-0.38.0rc1.tar.gz |
|---|---|
| Size | 286.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c576c284e924d7248a5c14ea4814ee2c93eb2d9500bc6de8219b521045354fe7
|
|
BLAKE2b-256 checksum How to use checksums |
50f8b3bddab6491ff663b545f0df5a3d188c72da9442275939ad7633714c3718
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logRelease files / qatlas_cli-0.38.0rc1-py3-none-any.whl
| Download URL | qatlas_cli-0.38.0rc1-py3-none-any.whl |
|---|---|
| Size | 128.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0015bfb4c2164b629a46b97c2a1dc7275553276924798fdaa54d82cb16d208dc
|
|
BLAKE2b-256 checksum How to use checksums |
3fcddad05e43e5404c2f3ed4b1976a9ff1bd08bca821490d0499b70275baecc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logSecurity for qatlas-cli 0.38.0rc1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for qatlas_cli-0.38.0rc1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.