Comprehensive guide to porting Django .96 apps to Django 1.0. Short version? You’re going to be doing a lot of boring, tedious work. Have fun.

Visit site:

http://docs.djangoproject.com/en/dev/releases/1.0-porting-guide

Comments

  1. 001 // Jacob Kaplan-Moss // 09.04.2008 // 4:41 AM

    It’s not too bad, I hope, but yeah there’s some pretty big changes — changes to templates to support autoescaping are a real pain in the ass, for one.

    At least it’s not as bad as the 0.91 -> 0.95 change; Matt reminded me of this gen from the release notes:

    The number of changes required to port from 0.91-compatible code to the 0.95 code base are significant in some cases. However, they are, for the most part, reasonably routine and only need to be done once.

    Ouch.

  2. 002 // Jeff Croft // 09.04.2008 // 6:40 AM

    Oh yeah — nowhere near as bad as .91 -> .95. I was just being facetious. While there are a lot of changes and I don’t envy the position anyone who hasn’t been tracking trunk all the way is in, Django 1.0 is sooooo much better than .96 that it’s all been absolutely worth it. :)

  3. 003 // Baxter // 09.04.2008 // 6:49 PM

    I’m one of the poor schlubs who wasn’t tracking trunk, at least on one site. So yeah, I got the big PITA of getting everything up to speed, and a lot of it took a long time to see any advantage. Newforms-admin thoroughly kicked my ass, and I still haven’t completely come to terms with the unicode merge.

    But then things start falling in place and it all starts making sense. A lot of sense.

    Great stuff.

Post your comment