Re:Django 1.9 Released
by pbreit on Tuesday December 01, 2015 @11:38PM
(#10661001)
But it shouldn't have sailed. Frameworks need to keep up with the times. That should be a benefit of frameworks. Should be possible while preserving backwards compatibility.
[ Parent
| on HN ]
Note that database migrations weren't part of Django until 1.7, before that they were provided by an external app (South).
Which meant that Django's database models couldn't migrate.
Even now, there is no real way to start with Django's own User model and switch your project over to a custom one later (because you'd have many database tables with foreign keys to the Django one). The current recommendation is to start new projects with a custom User model always.