Django

The slides from my presentation, Django and PostgreSQL, are now available.

(One of an occasional series of posts about strange errors you can get out of Django, and what it is trying to tell you.)

This exception was being thrown when I was trying to render a template:

1
dictionary update sequence element #0 has length 1; 2 is required

It turned out to be a slightly

I love Django a lot; it still surprises me how productive I can be in it. And, especially in more recent versions, the error handling for weird configuration problems is much, much better than it used to be.

But sometimes, you get an error whose origin is slightly mysterious. Thus, it can be helpful to have a log of

• PostgreSQL, When It’s Not Your Job from PGCon 2016.
• The PCI Compliant Database from PGCon 2016
• PostgreSQL Proficiency for Python People from PyCon US 2016.
• Django and PostgreSQL, an Ever-Closer Union from PyCon US 2016.

I’ll be speaking about Django and PostgreSQL at PyCon US 2016.

You can’t build a real-life system without caching.

That being said, it’s often the case that parts of the system you think are going to be slow aren’t. I’ve noticed a tendency to build out a huge stack of components (“we’ll have PostgreSQL, and Redis, and Celery, and Varnish, and…”) without actually measuring where the bottlenecks are.

Example:

My slides for Django 1.8 and PostgreSQL are available.

This is long, and involves drama. If you are not interested in the drama, I encourage you to skip it, and have a wonderful time at Djangocon US 2014.

–

I recently resigned as the program chair for Djangocon US 2014.

Up until now, I had been intending to simply wish Djangocon the best of success,

Just a reminder that the Djangocon US 2014 Call for Proposals ends July 15, 2014… we would love your talks and tutorials!

As program chair this year, I am very pleased to announce that the Call for Proposals for Djangocon US 2014 is now open! It only runs through the end of June, so be sure to get them in promptly!