就业培训     下载中心     Wiki     联络
登录   注册

 

 

  • 要求
  • 许可
  • 如何贡献
  • 如何安装 PyInstaller
  • PyInstaller 能做什么及如何做
  • 使用 PyInstaller
  • 运行时信息
  • 使用 Spec 文件
  • 有关特定特征的注意事项
  • 当事情出错时
  • 高级话题
  • 理解 PyInstaller 挂钩
  • 构建引导程序
  • PyInstaller 的变更日志
  • 信用
  • 手册页
  • 开发指南
    1. 首页
    2. PyInstaller 3.6
    3. 开发指南

    开发指南

    快速入门

    • 我们的 git 存储库在 https://github.com/pyinstaller/pyinstaller : 

      git clone https://github.com/pyinstaller/pyinstaller
      • Development is done on the develop branch. Pull-request shall be filed against this branch.
      • Releases will reside on the master branch.

    • 安装要求的测试工具： 

      pip install -r tests/requirements-tools.txt

    • Commit as often as you’d like, but squash or otherwise rewrite your commits into logical patches before asking for code review. git rebase -i is your friend. Read the »» Detailed Commit Guideline 了解更多信息。

      Reformatting code without functional changes will generally not be accepted (for rational see #2727 ).

    • Write meaningful commit messages.

      • The first line shall be a short sentence that can stand alone as a short description of the change, written in the present tense, and prefixed with the subsystem-name .
      • The body of the commit message should explain or justify the change. 阅读 »» Detailed Commit Message Rules 了解更多信息。

    • Provide tests that cover your changes and try to run the tests locally first.

    • Submit pull-requests against the develop branch. Mind adding a changelog entry so our users can learn about your change!

    • For new files mind adding the copyright header, see PyInstaller/__init__.py (also mind updating to the current year).

    • In response to feedback, squash the new “fix up” commits into the respective commit that is being fixed with an interactive rebase ( git rebase -i ). Push the new, rewritten branch 采用 git push --force . (Scary! But github doesn’t play nicely with a safer method.)

    开发者文档编制

    1. 首页