Upgrading Django (to 1.7)
summary
Django 1.7 is released and brings native migrations that replace South, a new app registry that provides historical models, and a built‑in system check command. The demo builds a Camelot app with a Knight model, shows creating migrations, adding a boolean trader field, and using runpython data migrations to mark Lancelot a traitor — the workflow runs and rolls back cleanly. initial_data fixtures are deprecated (use data migrations), South is incompatible with 1.7, and the release requires Python 2.7 while still supporting Python 3.
AI-written summary · about
chapters (22)
- 0:00Start
- 4:13Pre-Releases
- 5:10Version Support
- 5:36Deprecations
- 6:01Support Prior to v1.7
- 6:29With Arrival of v1.7
- 7:54Django 1.5
- 17:13Migrations History
- 18:11What is a migration?
- 23:01Step back!
- 35:17Migrations in 1.7
- 36:40South and 1.7
- 37:22Remove Migrations
- 37:37App Cache
- 37:58New App Registry
- 38:34Systems Check
- 39:16Customized ORM Interaction
- 39:56Upgrade Process
- 40:50Upgrade Schedule
- 42:29Practical knowledge
- 43:17Practical Upgrade Knowledge
- 43:55The Future?
related talks
23mBeyond the Basics of Migrations
21mMigrating to Success: Unleashing the Power of Django Migrations
27mMigrating legacy data to your Django project
32mContinuous Deployment and Release of Django Apps
33mPeaceful Django Migrations with Efe Öge
31mThis Old Pony: Working With Legacy Django Apps
01h 06mEffective Django
24mDjango as a Database Documentation Tool: The Hidden Power... with Ryan Cheley