5 ms·
Read the release notes: http://docs.djangoproject.com/en/dev/releases/1.3/ http://docs.djangoproject.com/en/dev/releases/1.3/ If there's no conflicting code c
by Refringe 16y ago
Read the release notes:
http://docs.djangoproject.com/en/dev/releases/1.3/ http://docs.djangoproject.com/en/dev/releases/1.3/
If there's no conflicting code changes compared to what you've already written, upgrade away!
If there are changes needed to support the new version you'll have to weigh the time needed to implement the changes to the new features/improvements in the new version; is it worth it? Only you can make that decision.
- jonknee 16y agoConsidering it's his first project and he just started, there's no reason to not be using the latest.
- bad_user 16y agoI upgraded an fairly complex application used in production, from Django 1.0 to 1.1, then to 1.2. Changes between successive versions rarely have backwards-compatibility issues and fixes are easy.