Django 1.10 released • Hacker News Board

Re: Django 1.10 released

#21

Post by heyts » Mon, Aug 01, 2016, 7:43 PM UTC

CuriouslyC wrote: post #20

heyts wrote: post #17

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 ;)

Admittedly but Backbone is _still_ a good intro to Front-end frameworks because it has a steep learning curve upfront instead of, say, angular that seems easy enough to pick up until you try to tackle non trivial applications.

Re: Django 1.10 released

#22

Post by bdr » Mon, Aug 01, 2016, 7:44 PM UTC

dchuk wrote: post #5

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 front-ends, the utility of both of these frameworks has gone down in absolute terms. When they first came out, front-end features like form generation and HTML templating were really important, but now they're arguably better to avoid. (That's why channels are so important to the future of Django.)

That said, I still like Django a lot and use it all the time. I don't want to discourage you from learning it. But I wouldn't do it because you're trying to make a leap from Rails.

Re: Django 1.10 released

#23

Post by bdr » Mon, Aug 01, 2016, 7:45 PM UTC

Walkman wrote: post #16

hrayr wrote: post #3

I'm still stuck with Django 1.4 for one of my projects, it's such a big hurdle to upgrade it. I wonder if it's worth to just straight up rewrite it in 1.10.

It's better to do it step by step: 1.4 to 1.5, 1.5 to 1.6, etc. You need to go through the release notes and have a good test coverage.

This. Go through the deprecation lists and backwards incompatibility lists item by item. Thankfully, they're very thoroughly done. It probably won't take as long as you think!

Re: Django 1.10 released

#24

Post by Flimm » Mon, Aug 01, 2016, 7:46 PM UTC

Here are the release notes, they are excellently written, just like the Django docs are excellently written. I continue to be impressed.

https://docs.djangoproject.com/en/1.10/releases/1.10/

Re: Django 1.10 released

#25

Post by St-Clock » Mon, Aug 01, 2016, 7:46 PM UTC

gtaylor wrote: post #4

hrayr wrote: post #3

I'm still stuck with Django 1.4 for one of my projects, it's such a big hurdle to upgrade it. I wonder if it's worth to just straight up rewrite it in 1.10.

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.

Re: Django 1.10 released

#26

Post by RussianCow » Mon, Aug 01, 2016, 7:50 PM UTC

CuriouslyC wrote: post #18

dchuk wrote: post #5

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?

There is no point unless you are going to using a lot of Python's scientific computing apparatus, or you want the ability to rewrite "hot" code in Cython for better performance. If you are primarily focused on social-esque or CRUD-heavy apps there isn't really an upside vs Rails.

What could you possibly be doing that you need those things within a Django app? If you're placing CPU-intensive and scientific code directly into your web app backend, I'd rethink your architecture before you consider switching languages.

Re: Django 1.10 released

#27

Post by orf » Mon, Aug 01, 2016, 7:55 PM UTC

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 suck now so that's a bonus.

Re: Django 1.10 released

#28

Post by stenius » Mon, Aug 01, 2016, 8:00 PM UTC

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.

Re: Django 1.10 released

#29

Post by plumeria » Mon, Aug 01, 2016, 8:00 PM UTC

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/...)

Re: Django 1.10 released

#30

Post by sold » Mon, Aug 01, 2016, 8:00 PM UTC

stenius wrote: post #28

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.

No, that's 1.11 (a LTS release)