Tutorials¶
Phase 1, weeks 1 to 4. I do these before I touch a ticket. I tick each box when the code runs on my machine, and reading alone does not count.
The Django tutorial¶
The polls app, in eight parts. Links go to the stable documentation.
- Part 1: a project, an app, a first view. Requests and responses.
- Part 2: the database, models, a first migration, the admin site.
- Part 3: views and templates.
- Part 4: forms and generic views.
- Part 5: automated tests.
- Part 6: static files.
- Part 7: customising the admin site.
- Part 8: third-party packages.
Part 2 and part 5 matter most for what follows: part 2 is where migrations first appear, and part 5 is how Django expects a change to be proven.
ORM topic guides¶
Week 4, once the polls app works.
- Models: fields, relationships,
Meta. - Making queries:
QuerySet, lookups, related objects. - Migrations:
makemigrations,migrate,sqlmigrate,showmigrations, thedjango_migrationstable. - Database transactions:
BEGIN,COMMIT,transaction.atomic.
Output of the week: a short note, in my own words, on what migrate does between BEGIN and COMMIT.
Contributing tutorial¶
- Writing your first contribution for Django: done before the session, with a practice patch.
Where the code lives¶
The polls project goes in my fork of django-local-test, so that the same project can later run against a local copy of Django. See Setup.
If the tutorials take longer than four weeks, they keep the priority and the contribution gets smaller. See Learning path.