书栈(BookStack.CN) 构建 Python 打包的解决方案目前有点混乱，因为有各种不同的工具。在本教程中，我们将使用 setuptools 建立我们的包。这是推荐的打包工具（与distribute分支合并后）。可是使用 pip 来安装和卸载它。你现在应该安装这两个软件包。如果需要帮助，你可以参考如何使用 pip 安装 Django。您可以用相同的方式安装 setuptools。 Python 当 Django 增加新特性，以及 Django API 或者其行为发生改变时，会补充相关内容到文档 中。 Django 文档和其代码使用同一份版本控制进行管理。它位于我们 Git 仓库的 docs 目录下。在 Git 仓库中，每一份在线文档都是独立的文本文件。 您可以通过多种方式阅读 Django 文档，根据优先级顺序排列如下： 文档是如何更新的 哪里可以获取文档 在线获取 接下来如何学习？ （tarball）的 docs/ 的目录下。 如果您正在使用开发版本的 Django (又名”trunk 版本”)，请注意 docs/ 目录包含了所有的 文档。您可以通过 git checkout 来获取最新更新。 一个稍微有点技术含量的查看文档的方法是通过 Unix 系统的 grep 命令来查找关键字搜索文 档。例如，这将会展示 Django 文档中每一处提及”

的 ID，这里需要注意 ID 是 Jenkins 中分配给对应密钥的 ID labels：标签，可以为任务打上自定义的标签，执行的时候可以区分标签来继续执行 mablBranch：分支，指定的话会执行对应分支下的所有测试集和用例 如果管道语法中有不想要配置的参数项，需要置空，保留参数名。 49 《51 测试天地》七十四 www.51testing.com 声明性管道： 脚本化管道： 功能成 熟的被测对象，开发阶段的软件最大的特点就是逻辑与功能变更频繁，那么基于快速灵 活的 CI 来说就是再适合不过了，我们可以按照自身产品测试业务的条件来设置合适的任 务触发条件，比如当某个分支的代码出现了改动，我们的测试任务就会自动执行，从而 在项目生命周期较早的阶段来进行测试介入与问题快速修复，从而有效降低整个项目的 开发成本。 当然，以上的这些都是一些比喻，真实的工作情况肯定要复杂的多，所以在

get it Differences between versions Writing your first patch for Django Introduction Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

Differences between versions Writing your first patch for Django Introduction Code of Conduct Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

Differences between versions Writing your first patch for Django Introduction Code of Conduct Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

Differences between versions Writing your first patch for Django Introduction Code of Conduct Installing Git Getting a copy of Django’s development version Rolling back to a previous revision of Django Running documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. Where to get it You can (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.11.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.11.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)

documentation is kept in the same source control system as its code. It lives in the docs directory of our Git repository. Each document online is a separate text file in the repository. 2.10.4 Where to get it (aka “trunk”), note that the docs/ directory contains all of the documentation. You can update your Git checkout to get the latest changes. One low-tech way of taking advantage of the text documentation documentation in our Git repository contains the “latest and greatest” changes and additions. These changes often include documentation of new features added in the Django development version – the Git (“trunk”)

Install the application from its GitHub repository using pip: pip install git+http://git@github.com/divio/django-polls.git#egg=polls Let’s add this application to our project. Add 'polls' to the end also places it in your virtualenv’s src directory as a cloned Git repository: pip install -e git+http://git@github.com/divio/django- polls.git#egg=polls You should end up with a folder structure similar GitHub repository to your own GitHub account 2. Clone your fork locally: git clone git@github.com:YOUR_USERNAME/django-cms.git 3. Create a virtualenv: virtualenv cms-develop source cms-develop/bin/activate