skywind3000 / skywind3000/PyStand
PyStand使用经验分享
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
首先感谢韦神，带来了这个非常优秀的工具。
我使用了PyStand一段时间，参考过本项目issues及韦神等大佬的文章，积累了一点点相关的经验。比如如何自定义启动脚本的路径，一键编译，如何从0开始搭建和管理Python环境， 如何用VS Code调试代码（支持断点和第三方库的语法补全），及pyqt、qml的中文路径问题等。也根据自己的需求修改过原项目代码。
本项目README和WiKi相对没那么丰富，所以我整理了一下自己的经验，写在 我的fork的README 里。也许可以给小白或者有需要的人提供一些参考，让不熟悉C++的人也可以一定程度上编译项目和自定义Python环境，及通过VS Code调试的方案。希望能为PyStand生态提供一点资料。
使用PyStand的项目示例： Umi-OCR
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository README and Wiki, then compare them with the contributor’s forked README at PyStand-Sora. Determine which setup, build, Python-environment, VS Code debugging, and path-related guidance is relevant to PyStand. Done means the documentation scope and proposed destination are agreed, with no reliance on undocumented material.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python, vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100