Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 1.7 alpha 1 released

djangoproject.com

Post reply on HN
Print view View original

11–20 of 23 posts

Re: Django 1.7 alpha 1 released

#11

Post by dominicrodger »

nzp wrote: post #10
christianmann wrote: post #7

Earlier quoted context omitted.

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

It has been stated by Andrew Godwin (author of South and the new native migrations) that there will be a clear path to switch from South to native migrations. And also for people who can't upgrade to 1.7 there should be South 2 with some of the new features backported from native migrations.

It's now documented and everything: https://docs.djangoproject.com/en/dev/topics/migrations/#upg...

Re: Django 1.7 alpha 1 released

#12

Post by alasdairnicol »

chrj wrote: post #8

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

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/

Re: Django 1.7 alpha 1 released

#15

Post by ProblemFactory »

christianmann wrote: post #7
shebson wrote: post #2

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…

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

The recommended upgrade path seems to be:

* Apply all South migrations to all database servers,

* Delete South migrations,

* Create new initial (create table) migrations for the current schema.

This makes sense, as migration code is supposed to be temporary. Migrations should exist in the codebase until the last database has them applied. Once all databases are up-to-date, it's better to delete them and "rebase" migrations to the current schema.

Old, fully applied migrations will still stay documented in the version control history, but they shouldn't be part of the master tree, much like obsolete code should be deleted instead of left commented out.

Re: Django 1.7 alpha 1 released

#16

Post by dkoch »

jmgutn wrote: post #14

> 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/

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

Re: Django 1.7 alpha 1 released

#17

Post by StavrosK »

cmsimike wrote: post #4

> 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...

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.

Re: Django 1.7 alpha 1 released

#18

Post by StavrosK »

ProblemFactory wrote: post #15
christianmann wrote: post #7

Earlier quoted context omitted.

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

The recommended upgrade path seems to be: * Apply all South migrations to all database servers, * Delete South migrations, * Create new initial (create table) migrations for the current schema. This makes sense, as migration code is supposed to be temporary. Migrations should exist in the codebase until the last database has them applied . Once all databases are up-to-date, it's better to delete them and "rebase" mig…

This has the added advantage of removing old, crufty migrations. We do this every few months, as there will usually be some problem that will prevent migrations from applying cleanly on new installations (someone made a mistake and reverted imperfectly, something collided and the resolution didn't delete some data, etc).

Re: Django 1.7 alpha 1 released

#19

Post by ovi256 »

alasdairnicol wrote: post #12
chrj wrote: post #8

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

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/

Hello, I'm interested in contributing to django, could you please give me a few pointers ? The django ticket list is daunting for a newcomer, that I don't know what to start with. My email's in the profile, and I'll be checking this comment as well. Thanks.

Re: Django 1.7 alpha 1 released

#20

Post by Walkman »

christianmann wrote: post #7
shebson wrote: post #2

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…

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

South2: https://github.com/andrewgodwin/south2 "This is the repository for South 2, the backport of Django's migrations code into a separate installable package for Django 1.4, 1.5 and 1.6."
Post reply on HN