A framework has two core roles: to protect us from dangerous things, and to protect us from tedious things.
My goal is to help keep the community informed of just how much development is going on, and where they can help. I hope to release a fresh updated every fortnight (that's two weeks for our American viewers - a contraction of "fourteen night").
and points where more feedback from the community is sought for a design decision.
None of this is new. None of this is hidden. It's always been there for everyone to see, but it may have just been too tedious to gather.
Django 1.6.1 has released, with quite a sizable list of bug fixes.
There's work afoot to move the decision of which lookups are available on a field onto the field itself.
This would, for instance, allow a DateTime field to list that it supports "__date", or that a GeoDjango Point field supports "__distance_lt".
This could potentially remove the need for GeoDjango to be separated as it is, but also open the gates on support for Postgres JSON fields, and more!
If you want to know more, hit up akaariai on IRC, who has been working on this for quite some time.
To help ease migrating to Django 1.6, there's a new "manage.py check" command, which will warn you of many detectable backward-incompatible changes.
Well, that's it for this edition, folks. Hopefully next cycle I'll have more news, updates, and exciting things to look at!
Animal Help Now, honoring Kevan Swanberg donated to the Django Software Foundation to support Django development. Donate today!