Django 1.7 alpha 1 released

[cmsimike]

> Applications can run code at startup, before Django does anything else, with the ready() method of their configuration.

I have been waiting for something like this for a very long time. No more wondering where signals should go. [0]

[0]https://docs.djangoproject.com/en/dev/ref/applications/#djan...

[StavrosK]

God, yes. I even asked for a signals.py so they could be declared there, but this is even better. I'm very excited about this.

[hannes2000]

yes! No more circular imports because of signal receivers being added to models.py. Super excited about this.

[shebson]

It's great to see schema migrations move into Django core. South is great, but Django will be much better with schema migrations baked in, especially for newcomers.

For anyone coming to Django from Rails, South seems anomalous. Outside of database migrations, Django is a very battery-included framework, so it's weird that until 1.7 data migrations were handled by third party tools (mostly South) and not mentioned at all in the Django documentation.

This is a big step for Django. I'm excited for the (not too distant) future when 1.7 is the official release.

[semerda]

Totally agree. It is such an important part of a Django project where Models are involved. Every release of Django brings exciting and well thought through features. Future looks great for this awesome Python framework!

[christianmann]

I wonder if there will be a tool to convert (migrate?) South migration data to Django's native format.

[acjohnson55]

Django's all grown up! I'm pretty psyched about this release. Obviously, the long-awaited migrations functionality is the centerpiece, but for a framework without that many rough edges, they do such a great job of finding the ones that remain and terminating them. Looking forward to the end of magical models.py behavior; to stronger support for apps; easier to use custom QuerySets and reverse relation Managers; and Lookups, Transforms, and custom prefetching in the ORM. This is looking like the most exciting release since 1.4 for tightening up the core of the framework.

Anybody have any insight into what's next?

[jsmeaton]

Potential things for 1.8 that I'm aware of are composite fields and improved aggregates. Hopefully, there'll also be some work on .values(), .annotate(), and .order_by() that will allow a much broader range of options, which is part of a larger internal refactor of the ORM. No guarantees on any of the above though.

[jmgutn]

> Additionally, users of South (a popular third-party package for schema migrations) should note that South is not compatible with the 1.7 alpha.

Is this because of the new migrations built-in module? [0]

[0]https://docs.djangoproject.com/en/dev/topics/migrations/

[dkoch]

Yes. The author of South is writing the built-in migrations, and keeping a 3rd party migration library would be redundant.

[chrj]

Wasn't the "New system check framework" already in 1.6? I remember seeing warnings about BooleanFields without defaults.

[alasdairnicol]

I wrote that BooleanFields without defaults patch! I'm glad that the warning has been seen by at least one person!

The ./manage.py validate command has been replaced with ./manage.py check in Django 1.7. The new system checks framework [1] is extensible, so third party apps will be able to add their own checks.

[1]: https://docs.djangoproject.com/en/dev/ref/checks/

[jsmeaton]

Internal validate code was spread right around the framework in various places. It has been refactored into a single, extensible location.

[nkuttler]

The (preliminary) release notes are full of nice things https://docs.djangoproject.com/en/dev/releases/1.7/

[collyw]

Only a week or so after I upgraded to 1.6