I've never been completely happy with this spindly and slightly confusing diagram from the Django Book, ever since it appeared the first edition.
Google are introducing paid-for extensions to Google App Engine quotas, which is great as it lets you build more complex applications if you're willing to pay the rates. At the same time they're reducing the baseline free quotas.
A summary of OGN9, originally on the Google Open Source Blog:
On Wednesday 22 October, over a hundred geeks attended the ninth Oxford Geek Night, upstairs at the Jericho Tavern.
As discussed previously, at Torchbox we recently built TimeToLead.eu, an advocacy site set up by the four major environmental NGOs to prompt MEPs into passing the sort of legislation the world's climate desperately needs. The project itself needed a fast turnaround time, and its pan-European audience demanded strong i18n and l10n.
In Django, when you have a queryset---a set of objects returned by an object manager, as yet not evaluated to actual objects---and you want them ordered randomly, set your order_by parameter to be a string of a single question mark:
>>> from mysite.models import Country
>>> Country.objects.order_by('?')
>>> Country.objects.filter(continent='Europe').order_by('?')
The objects should then be iterable in a random order.
Astonishingly, the existing documentation has very little Goo
Django continues to gather momentum towards its imminent 1.0 release. The 1.0 beta 1 is out; the developer documentation has been refactored; it already places nicely with Python's powerful debugging and logging tools; indeed, all is proceeding according to the roadmap, more or less.
To the untrained eye, you might think that you can put any old string in as the second element of one of your Django URL dispatcher patterns in urls.py:
Django’s templating language is intentionally quite restrictive. The idea is that you have to do all your data munging in the control-ish sublayer of the view layer, in the method registered as handling the view in urls.py. In principle this simplifies templates, but in practice it can make life for the developer more difficult: you have to really think ahead, and assemble your variables properly, so that the templating language can use simple iterative loops to prepare your HTML.
I wish Simon Willison had written about Django logging and debugging earlier than today. That way I wouldn’t have used the slightly daft solution I describe in the comments.
Of course, much earlier than today, and he’d have had to have written it before giving the talk that it was based on, which might sound a bit demanding on my part. But hey! I don’t make the rules.