Class-based generic view is a nice addition. I remember when I was learning Django and going through the official tutorial, that was one part that took me a while to understand. Kudos guys!
Django 1.3 released
21–30 of 42 posts
Re: Django 1.3 released
#22So as someone who has just started my first Django project, is there any reason not to immediately switch to 1.3?
Read the release notes: 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.
Considering it's his first project and he just started, there's no reason to not be using the latest.
Re: Django 1.3 released
#23So as someone who has just started my first Django project, is there any reason not to immediately switch to 1.3?
Read the release notes: 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.
I 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.
Re: Django 1.3 released
#24Class-based generic view is a nice addition. I remember when I was learning Django and going through the official tutorial, that was one part that took me a while to understand. Kudos guys!
People have been using the term 'class-based views' to describe the new feature but am I right in thinking this only affects generic views?
Re: Django 1.3 released
#25Class-based generic view is a nice addition. I remember when I was learning Django and going through the official tutorial, that was one part that took me a while to understand. Kudos guys!
People have been using the term 'class-based views' to describe the new feature but am I right in thinking this only affects generic views?
Well, it affects generic views, yes. They also have several mixins that you can use in other views.
Re: Django 1.3 released
#26So as someone who has just started my first Django project, is there any reason not to immediately switch to 1.3?
Almost certainly not, but digesting the release notes will let you make a more informed decision.
I agree. Switch immediately if you're just learning or playing around with Django. Most likely, the biggest change in casual development will be the class-based generic views, which I think are an improvement over the previous function-based generic views.
Re: Django 1.3 released
#27Class-based generic view is a nice addition. I remember when I was learning Django and going through the official tutorial, that was one part that took me a while to understand. Kudos guys!
People have been using the term 'class-based views' to describe the new feature but am I right in thinking this only affects generic views?
No, you can make your own class based views with the 1.3 codebase. The docs describe them as replacing Generic Views, but nothing stops you from creating your own class hierarchy that inherits from the base TemplateView (http://docs.djangoproject.com/en/1.3/ref/class-based-views/#...)
Re: Django 1.3 released
#28Congrats to the Django team! :) I'm in love with your API.
Re: Django 1.3 released
#29Glad to see it!
Some of the new stuff is really cool, and means I won't have to rely on external libraries anymore (like passing context variables in template includes).
Also, the new logging functionality is really great!
Keep up the good work!
Re: Django 1.3 released
#30So as someone who has just started my first Django project, is there any reason not to immediately switch to 1.3?
Most people dev off of trunk when they're starting out, actually. If you're doing that, 1.3 doesn't offer anything exciting.
That was the case until 1.0, but I don't think that's really the case since the 1.0 release, let alone later ones. That may have taken off again due to the 1.3 delays, but that's not a trend.
Point releases are supported, with clear changelogs and migration paths and available from pypi. They're really much easier to work with than trunk.