31–40 of 122 posts
Earlier quoted context omitted.
1.4 to 1.5 is the really painful upgrade. The rest are much less so. Especially after 1.6.
Until you hit the migrations in 1.7. But you are right. At my previous job, I spent countless hours getting from 1.4 to 1.5, but the step from 1.5 to 1.6 was relatively painless.
Edit: looks like this is now the 2nd to last release to support Python2. Original: It doesn't mention it on this page, but this is also planned to be the last Django release to support python2. Django 2 will require python3.
Now that the transition is in full swing, it's encouraging to see more projects adopt a Python 3 First attitude.
I only wish Ansible would catch up (a recent release broke the core Python 3 support that was there, and no-one seemed to care as Py3 isn't yet officially supported).
Edit: looks like this is now the 2nd to last release to support Python2. Original: It doesn't mention it on this page, but this is also planned to be the last Django release to support python2. Django 2 will require python3.
Earlier quoted context omitted.
1.4 to 1.5 is the really painful upgrade. The rest are much less so. Especially after 1.6.
Until you hit the migrations in 1.7. But you are right. At my previous job, I spent countless hours getting from 1.4 to 1.5, but the step from 1.5 to 1.6 was relatively painless.
I wonder why this release didn't include the class-based auth views ( https://github.com/django/django/blob/1.10/django/contrib/au... vs https://github.com/django/django/blob/master/django/contrib/... )
I wonder why this release didn't include the class-based auth views ( https://github.com/django/django/blob/1.10/django/contrib/au... vs https://github.com/django/django/blob/master/django/contrib/... )
Django has a time based release schedule [1]. The class based authentication views weren't committed until after the feature freeze for the 1.10 alpha.
Earlier quoted context omitted.
If you plan to use Django as an API server, you might be interested in Lightweight Django ( http://shop.oreilly.com/product/0636920032502.do ), which shows you how to design and build an API server using Django, Django Rest Framework (another great Django related project) and Backbone on the front-end.
2010 called, it wants its tech stack back ;)
Now get off my lawn.
As a Rails dude...is there any reason for me to learn Django at all? Everything I've heard about it is that it provides a lot of sane defaults (like Rails) but has much less "magic" than Rails is typically thought to have. And if the answer to my question is yes, what books/tutorials/screencasts/courses to people recommend to get started with?
As someone who picked Django over Rails ~10 years ago and has used it for everything since then-- I wouldn't bother. Django and Rails, like Python and Ruby, look more and more similar as time goes on. Not because they are becoming more similar, but because the web ecosystem around them has become a lot more diverse. If you want a break from Rails, learn Phoenix! Or Node, I guess. Furthermore, with the advent of fat f…
I was personally a Rails guy, then switched to learning Django, but had the experience you note...both frameworks solved many problems which aren't as relevant in this age of SPAs. I suppose if you really liked Django's ORM it might be worth it, but doubt there's a huge amount of value to be gained. YMMV.
As a Rails dude...is there any reason for me to learn Django at all? Everything I've heard about it is that it provides a lot of sane defaults (like Rails) but has much less "magic" than Rails is typically thought to have. And if the answer to my question is yes, what books/tutorials/screencasts/courses to people recommend to get started with?
The typical recommendation to getting started with Django, is to go through the tutorial included in the documentation [0]. This is the path I took several years ago, it'll get you up and running in no time. I found Two Scoops of Django[0] to be a great resource if you want to follow the best practices for a Django app. The authors are also very active in the community. [0] https://docs.djangoproject.com/en/1.10/intr…
Shame about Channels, but I see the logic in not including it. Django is pretty awesome as a backend, and while it's not a 'cool' framework anymore (I feel old!) it's amazing for writing back-office applications. I use it as an API backend with Django-rest-framework. The advantage is you get ridiculous amounts of packages that all integrate with Django that does pretty much anything you want. Also the ORM doesn't suc…