copy of Django’s development version Running 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 “view”, and the View the “template”. How come you don’t use the standard names? does <feature Y> – why doesn’t Django? Why did you write all of Django from scratch, instead of using other Python this feature of Django in the tutorial. path() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows

this feature of Django in the tutorial. path() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. 2.7.3 Writing our first test We identify a bug Fortunately changes and additions. These changes include documentation of new features targeted for Django’s next feature release. For that reason, it’s worth pointing out our policy to highlight recent changes and additions

copy of Django’s development version Running 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 “view”, and the View the “template”. How come you don’t use the standard names? does <feature Y> – why doesn’t Django? Why did you write all of Django from scratch, instead of using other Python this feature of Django in the tutorial. path() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows

“view”, and the View the “template”. How come you don’t use the standard names? does <feature Y> – why doesn’t Django? Why did you write all of Django from scratch, instead of using other Python this feature of Django in the tutorial. path() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. Writing our first test We identify a bug Fortunately

this feature of Django in the tutorial. path() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. 2.7.3 Writing our first test We identify a bug Fortunately version, we try to update the documentation in the same Git commit transaction. • To distinguish feature changes/additions in the docs, we use the phrase: “New in version X.Y”, being X.Y the next release

“view”, and the View the “template”. How come you don’t use the standard names? does <feature Y> – why doesn’t Django? Why did you write all of Django from scratch, instead of using other Python this feature of Django in the tutorial. url() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. Writing our first test We identify a bug Fortunately

this feature of Django in the tutorial. url() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. 2.7.3 Writing our first test We identify a bug Fortunately version, we try to update the documentation in the same Git commit transaction. • To distinguish feature changes/additions in the docs, we use the phrase: “New in version X.Y”, being X.Y the next release

“view”, and the View the “template”. How come you don’t use the standard names? does <feature Y> – why doesn’t Django? Why did you write all of Django from scratch, instead of using other Python this feature of Django in the tutorial. url() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. Writing our first test We identify a bug Fortunately

this feature of Django in the tutorial. url() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows it’s fruitful to write your first test the next time you make a change, either when you add a new feature or fix a bug. So let’s do that right away. 2.7.3 Writing our first test We identify a bug Fortunately version, we try to update the documentation in the same Git commit transaction. • To distinguish feature changes/additions in the docs, we use the phrase: “New in version X.Y”, being X.Y the next release

copy of Django’s development version Running 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 “view”, and the View the “template”. How come you don’t use the standard names? does <feature Y> – why doesn’t Django? Why did you write all of Django from scratch, instead of using other Python this feature of Django in the tutorial. path() argument: name Naming your URL lets you refer to it unambiguously from elsewhere in Django, especially from within templates. This powerful feature allows