Oh they do break, but it's a much slower process than RoR (as you described)
IIRC the most impacting changes I remember were in Config, replacement of South with a native solution and some timezone issues
IIRC the most impacting changes I remember were in Config, replacement of South with a native solution and some timezone issues
The documentation was telling something like: Ensure you applied all previous migrations and then start from scratch. Thats not an upgrade path. It may work for standalone web applications, but I have a python project (packaged as deb/rpm package and using the packaged django version of different distributions) that should work with multiple django versions and the user may upgrade the django version at any point.
I had to write raw sql statements to get the mirgration status of south (after the upgrade, without a working version of south anymore) and "fake" apply the migrations of the new native solution.