Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 1.10 released

djangoproject.com

Post reply on HN
Print view View original

91–100 of 122 posts

Re: Django 1.10 released

#91

Post by rtpg »

jsmeaton wrote: post #89
rtpg wrote: post #85

Earlier quoted context omitted.

Ah, I feel bad, because I ran into this twice and didn't report this properly. The situations I ran into happened whenever I would combine filters and excludes, along with some joins. The system would simply drop filters, and just do a plain SELECT on the table. But ever since the 1.8 ORM update, I have no longer been able to reproduce this, so have assumed it was fixed through cleaning up the internals. I did report…

Exclude filters are awful and very unintuitive if you know SQL in my experience. I'd much prefer to use negated filters like: `.filter(id__notequal=3)`. I'm giving a talk at djangocon AU in a couple of weeks where I'll step through examples like this.

Right. Worse case, you can use `~Q` or the like. The way I recall it, this didn't solve the issue (as in: something more fundamental than "using exclude instead of filter"), but I no longer have the example...

Re: Django 1.10 released

#92

Post by wyldfire »

__jal wrote: post #37
CuriouslyC wrote: post #20

Earlier quoted context omitted.

2010 called, it wants its tech stack back ;)

Half-implemented, broken and cool is more fun than solid and battle-tested, and that's perfectly fine so long as you don't get yourself fired over a bad choice - have a great time. Honestly, I used to be more novelty-driven, too. But battle-tested and boring has its place. Now get off my lawn.

Sorry, the off-lawn module depends on left-pad. :(

Re: Django 1.10 released

#93

Post by brianwawok »

xlxlxlx wrote: post #82
ubernostrum wrote: post #69

Earlier quoted context omitted.

Channels will get there. It just wasn't quite ready on time for 1.10. Hopefully it will be ready on time for 1.11, and then it'll ship in Django.

I just used Channels in a personal project and it's great! My requirements were mostly basic and I haven't put it into production yet, but everything has gone smoothly so far.

What did you do with it? I still haven't figured out what to do with them...

Re: Django 1.10 released

#94

Post by brianwawok »

davb wrote: post #32
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.

This is great news. 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).

Ansible problem is 100s of libs that are python2 only. Sysadmins never got python3...

Re: Django 1.10 released

#95

Post by brianwawok »

bdr wrote: post #49
wandering2 wrote: post #46

Earlier quoted context omitted.

>front-end features like form generation and HTML templating were really important, but now they're arguably better to avoid. Why is that?

It's the DRY principle. If you have a single-page app, the frontend needs to know how to render everything (using JS), so rendering on your backend as well is, at best, duplicated work. There may also be complications at the boundary of those regimes, like how your frontend initializes on top of server-rendered HTML.

At most 5% of apps should be a SPA. Seems rash to pick your only web framework on 5% of apps.

Re: Django 1.10 released

#96

Post by mozumder »

encoderer wrote: post #84

If there are any Django masters in the building: If you were starting a project today would you use 1.10 or stick with the LTS release (1.8)? I have a fairly mature django project using 1.6 that I would be borrowing a bit from, and my experience not upgrading off 1.6 due to pain makes it feel like an LTS path might be a good choice?

1.10.

Always start new projects with the latest version. You don't want to be stuck on really old versions when you eventually upgrade.

Re: Django 1.10 released

#97

Post by ataylor32 »

jsmeaton wrote: post #90
encoderer wrote: post #84

If there are any Django masters in the building: If you were starting a project today would you use 1.10 or stick with the LTS release (1.8)? I have a fairly mature django project using 1.6 that I would be borrowing a bit from, and my experience not upgrading off 1.6 due to pain makes it feel like an LTS path might be a good choice?

The next LTS will be released in about 9 months. If you're willing to make a small upgrade at that time, I'd build on 1.10 and then upgrade to 1.11 LTS, which will give you 3 years (I think..) plus 9 months of 1.10 support. Moving from 1.8 to 1.11 shouldn't require any changes provided that you're running with 0 deprecation warnings on 1.8. The new release scheme means that if you're running on an LTS with no depreca…

> Moving from 1.8 to 1.11 shouldn't require any changes provided that you're running with 0 deprecation warnings on 1.8.

Yes, this is how it's supposed to be. This agrees with Django's roadmap (see the "I’m the maintainer of a reusable application. Which Django versions should I support?" question at the bottom): https://www.djangoproject.com/weblog/2015/jun/25/roadmap/

However, it depends on the third party apps you're using. I have a Django 1.9 site that uses django-mptt. The site was running warning-clean, but when I attempted to upgrade the site to Django 1.10, it broke because of this issue: https://github.com/django-mptt/django-mptt/issues/469

Re: Django 1.10 released

#98

Post by asimuvPR »

encoderer wrote: post #84

If there are any Django masters in the building: If you were starting a project today would you use 1.10 or stick with the LTS release (1.8)? I have a fairly mature django project using 1.6 that I would be borrowing a bit from, and my experience not upgrading off 1.6 due to pain makes it feel like an LTS path might be a good choice?

The upgrade to 1.8 should not be difficult. It all depends how you are setup now. I write django fulltime. Ping me if you need help. :)

Re: Django 1.10 released

#99

Post by asimuvPR »

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.

No need to rewrite if you have a good codebase. Just go upgrade one version at a time until you reach your target version. Its not too bad.

Re: Django 1.10 released

#100

Post by xlxlxlx »

brianwawok wrote: post #93
xlxlxlx wrote: post #82

Earlier quoted context omitted.

I just used Channels in a personal project and it's great! My requirements were mostly basic and I haven't put it into production yet, but everything has gone smoothly so far.

What did you do with it? I still haven't figured out what to do with them...

I made something like a cross between a chat room and reddit. There are any number of possible rooms (like subreddits), with new top level posts popping up in real time, and when you click on a post, it expands and the replies become visible as a comment chain. It's not done yet though. For a while now I've been trying to do as much as I can on a single project for one week, and then start another. I definitely plan to come back to this one when I can.

This week I'm using Channels again too. I'm making a head-to-head Minesweeper web app where you can challenge and compete against other players. After finding an opponent, essentially you'll see your own board and your opponent's board side by side, and each players' progress is broadcast in real time via Channels to one another.

Post reply on HN