Django’s test suite for the first time Working on a feature Creating a branch for your patch Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second Getting Help section of the FAQ. Installing Django Debug Toolbar Django Debug Toolbar is a useful tool for debugging Django web applications. It’s a third-party package maintained by the Jazzband organization this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should

Django Running Django’s test suite for the first time Creating a branch for your patch Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second time Writing this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should you’re maintaining several Django projects. When they do, the best solution is to use virtualenv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries

Django’s test suite for the first time Working on a feature Creating a branch for your patch Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should you’re maintaining several Django projects. When they do, the best solution is to use virtualenv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries

Django’s test suite for the first time Working on a feature Creating a branch for your patch Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should once you’re maintaining several Django projects. When they do, the best solution is to use venv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries

Django’s test suite for the first time Working on a feature Creating a branch for your patch Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should once you’re maintaining several Django projects. When they do, the best solution is to use venv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries

this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should you’re maintaining several Django projects. When they do, the best solution is to use virtualenv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries Getting started Django Documentation, Release 1.10.9.dev20171123183751 • Running Django’s test suite. • Writing a test for your patch. • Writing the code for your patch. • Testing your patch. • Submitting

this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should once you’re maintaining several Django projects. When they do, the best solution is to use venv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries • Installing Git. • Downloading a copy of Django’s development version. • Running Django’s test suite. • Writing a test for your patch. • Writing the code for your patch. • Testing your patch. • Submitting

revision of Django Running Django’s test suite for the first time Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second time Writing Documentation this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should you’re maintaining several Django projects. When they do, the best solution is to use virtualenv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries

this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should you’re maintaining several Django projects. When they do, the best solution is to use virtualenv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries following: • Installing Git. • How to download a development copy of Django. • Running Django’s test suite. • Writing a test for your patch. • Writing the code for your patch. • Testing your patch. • Generating

Django Running Django’s test suite for the first time Creating a branch for your patch Writing some tests for your ticket Writing the code for your ticket Running Django’s test suite for the second time Writing this tutorial, we’re going to use setuptools to build our package. It’s the recommended packaging tool (merged with the distribute fork). We’ll also be using pip to install and uninstall it. You should you’re maintaining several Django projects. When they do, the best solution is to use virtualenv. This tool allows you to maintain multiple isolated Python environments, each with its own copy of the libraries