February archive

Django Update - 2014-02-09 to 2014-02-22

February 24, 2014


Oops, a bit late this time around. That's what I get for doing more things than I ought!


Lots of people are preparing their GSoC submissions, and the ideas are in hot discussion. One of the most active discussions is about replacing the venerable, but much maligned, Django Template Language with Jinja2.

Ticket Movement

Short lived tickets: 58

Tickets Created: 46

Open tickets: 1391 (-15)


The developers of the Unsetting Project have raised their hands, and asked for more input from the community. Their goal is, as I understand it, to provide two API layers for Django - one that we're familiar with, and the other below it not requiring settings.py

Did you know?

The {% regroup %} tag doesn't sort your data, so if you're not careful it may produce multiple groups with the same 'grouper' value. However, sometimes you may want this...


Sorry I'm late this cycle, folks, but I'm sure you don't mind.

And remember, if you've anything you think the community might benefit from, please drop me a line...

-- Have a better one!

Kickstarting Improved PostgreSQL support for Django

February 17, 2014

Django has always been a database agnostic framework. If we add a database-facing feature, we make sure that it works on SQLite, MySQL, PostgreSQL and Oracle. However, in the real world, some individual databases have some extraordinary features that others do not. While it is usually possible to access those features in some way, they don't have first class support in Django.

Django core team member Marc Tamlyn would like fix this situation, and develop a contrib library exposing all the interesting features of PostgreSQL to Django users.

However, to do this he needs the community's help. Developing this sort of functionality takes time, and that time can be hard to find in a busy schedule. To help fund development, Marc has launched a project on Kickstarter. The funds will be used to pay for Marc's time so that he can finish work on the codebase and get it ready for inclusion in Django.

You can find a lot more details about Marc's plans on the Kickstarter project page. The project met it's funding goal very quickly, but Marc has provided a bunch of very tantalising stretch goals which would be extremely interesting features for Django (and in some cases, would even be cross database compatible!)

The Django Software Foundation and the Django Core team have both endorsed this effort; the DSF has donated £1000 towards the project. We hope that you will join us in supporting Marc's Kickstarter project.

Django Update - 2014-01-26 to 2014-02-08

February 9, 2014


And the hits just keep on coming! This time around we've got more releases, more meets, and... well, more of (almost) everything!


Right on the back of the 1.7alpha1 release, we now have a 1.7alpha2. Turns out there was some nasty interaction between the new system checks framework and the changes made to app loading.

Google's "Summer of Code" is coming up [coming? it's summer now for some of us!] so it's time to start getting your submissions ready. Don't be scared - the core devs are really a friendly bunch :)

It seems Django has been getting some attention in the land of the Blue... IBM have contributed a Python driver and Django backend. You can read more about it here.

Ticket Movement

Short lived tickets: 48

Tickets Created: 42

Open tickets: 1406 (+10)


Adam Spence has offered to donate his Bootstrap based redesign of Admin. How do people feel about that? Some might say it would only encourage people to use Admin for purposes it's not designed. Others may say it's removing another road-block from making Admin more flexible.

Did you know?

There's a handy Django Development Dashboard you can use to watch how development is progressing over time.


Writing this update is harder than I'd expected. However, some people have made an effort to send me some positive feedback, which although it doesn't sound much, does make a difference.

So... thanks!

-- Have a better one!

Django 1.6.2 and Django 1.7a2 released

February 6, 2014

Today we're releasing Django 1.6.2, the latest bugfix release in the 1.6 series, and Django 1.7a2, the second alpha preview of the upcoming 1.7 release.

Django 1.6.2

Django 1.6.2 is the second bugfix release for the Django 1.6 series. Most bug fixes are minor; you can find a complete list in the Django 1.6.2 release notes.

All users are encouraged to upgrade to Django 1.6.2 at your earliest convenience. You can install Django using pip or download Django 1.6.2 from the Django downloads page. As always signed checksums of the package are available.

Django 1.7 alpha 2

Django 1.7 alpha 2 is a preview/testing release that represents the next stage in the 1.7 release cycle. It's an opportunity for you to try out some of the big changes coming in Django 1.7.

We're making a second alpha release for Django 1.7 after we discovered a bad interaction between the new system checks framework and the changes made to app loading. Because these changes made 1.7a1 particularly unstable, we're taking the step of releasing a second alpha.

For full details of what's new in Django 1.7, see the in-development 1.7 release notes.

As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the alpha package from our downloads page. And as always, signed MD5 and SHA1 checksums of the 1.7 alpha package are available.