Publish to PyPI so pipx install windows-autoclicker works

未关闭
#118 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
github-actions, python

调研方向

Start with pyproject.toml and the tag release workflow; the issue also points to README lines 137–140 and the landing page install section. Review the metadata cleanup dependency before reserving the package name, then check the release workflow’s build and publishing steps. Done means tagged releases publish checked wheel and sdist artifacts and pipx install windows-autoclicker installs the latest release.

由索引模型根据 Issue 内容生成。

描述

marketing packaging priority: low

Why it matters

Python users and scripters (the CLI/headless audience) expect pipx install <name>. Today the README tells them to install from a git URL, which is slower, harder to pin and invisible to PyPI search.

Evidence

  • README:137-140 recommends pipx install git+https://github.com/TMHSDigital/autoclicker.git.
  • https://pypi.org/pypi/windows-autoclicker/json returns 404; the name is free.
  • pyproject.toml already has a complete [project] table and #58 fixed wheel icons.

Suggested approach

  • Add a pypi job to the tag release using Trusted Publishing (OIDC, no stored token), building sdist + wheel with python -m build and running twine check.
  • Reserve the name now with a 1.6.x upload.
  • Update README and landing page install sections; add a PyPI badge.
  • Depends on the metadata cleanup issue so the PyPI page looks right.

Done when

pipx install windows-autoclicker installs the latest release, and the release workflow publishes automatically on tags.

主要语言
Python
星标
0
派生
2
平均合并
2 天 13 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。