Django Diaries

Why is Channels designed like it is, and what does it really mean for Django, Python, and WebSocket handling?

Progress on Django Channels, and working out how the different parts will talk to each other.

Django migrations have come a long way, but it stands on the shoulders of one project that has come just a little bit further.

Workflows, teams committing conflicting VCS branches, foreign keys being annoying and more feature in this week's Django Diaries.

This week, it's the exciting story of one man's battle against his idea of automatically writing settings files.

A week on a remote island leads to a lot of squashed things. I'm not entirely sure if they're related.

Migrations grow two exciting new operations as well as a new command, squashing two of my oldest feature requests.

Long, hard days of coding, shuffling and teasing Oracle finally come to a close - or do they?

Old South bugs and nemeses get eliminated, multi-database support might finally exist, and the merge is in sight.

It turns out that eradicating syncdb is not quite as easy as it should be...

I love it when a plan comes together. Especially when that plan involves so many tiny pieces of code.

This week sees django.db.migrations gain Operations, an Executor, and new command plans.

A new release of an old friend, and more news on django.db.migrations.

Welcome to the first of my Django Diaries, where I'll be detailing the progress I'm making on my Schema Alteration project.