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

Django 3

docs.djangoproject.com

Post reply on HN
Print view View original

11–20 of 196 posts

Re: Django 3

#11

Post by haolez »

scarygliders wrote: post #6

Right as I was just about to start a new Django project... The thought going through my mind right now is "I wonder if there is some way of creating a Django project and make it resilient to future Django updates and releases with minimum fuss?" I've had to deal with ongoing and inherited legacy projects which run on Python 2.7, use the long-deprecated Pylons, for which there is no easy upgrade path other than a tota…

Some languages are more prone to prioritize of your previous investment. The most popular examples are Java, C# and Go. Different tools for different needs.

Re: Django 3

#12

Post by pytester »

scarygliders wrote: post #6

Right as I was just about to start a new Django project... The thought going through my mind right now is "I wonder if there is some way of creating a Django project and make it resilient to future Django updates and releases with minimum fuss?" I've had to deal with ongoing and inherited legacy projects which run on Python 2.7, use the long-deprecated Pylons, for which there is no easy upgrade path other than a tota…

>Right as I was just about to start a new Django project...

It's rarely a good idea to use the latest version of Django simply because most projects will be reliant upon 3rd party libraries which will often be slow to catch up to supporting the latest version.

Re: Django 3

#13

Post by Scarblac »

scarygliders wrote: post #6

Right as I was just about to start a new Django project... The thought going through my mind right now is "I wonder if there is some way of creating a Django project and make it resilient to future Django updates and releases with minimum fuss?" I've had to deal with ongoing and inherited legacy projects which run on Python 2.7, use the long-deprecated Pylons, for which there is no easy upgrade path other than a tota…

The difference between 2.2 and 3.0 is quite small, as you can see in the release notes. Most projects won't need changes.

Re: Django 3

#14

Post by ageitgey »

bicx wrote: post #5

Does Python still have performance issues? That's always been my concern when considering its adoption.

The are some new-ish features like async and there some new parallelization options in 3.8 that help in some very specific cases, but generally you choose Python because you value development speed more than execution speed.

You can use Python (or Ruby, etc) to build fast websites that scale well if you are smart about how you use it and how you design your application, but it still isn't a particularly fast language compared to others.

Re: Django 3

#15

Post by senko »

scarygliders wrote: post #6

Right as I was just about to start a new Django project... The thought going through my mind right now is "I wonder if there is some way of creating a Django project and make it resilient to future Django updates and releases with minimum fuss?" I've had to deal with ongoing and inherited legacy projects which run on Python 2.7, use the long-deprecated Pylons, for which there is no easy upgrade path other than a tota…

> "I wonder if there is some way of creating a Django project and make it resilient to future Django updates and releases with minimum fuss?

Have lots of automated tests. The more surface area you cover, the easier it'll be to upgrade.

> [...] use the most basic and generic Django features, but even then what's to say those won't get deprecated in favour of some new exciting replacement?

In my experience, Django maintainers are slow to rush to new exciting replacements, and even slower to deprecate and remove things. From a compatibility perspective and ongoing maintenance, it's a great approach!

Re: Django 3

#16

Post by StavrosK »

danpalmer wrote: post #10
scarygliders wrote: post #6

Right as I was just about to start a new Django project... The thought going through my mind right now is "I wonder if there is some way of creating a Django project and make it resilient to future Django updates and releases with minimum fuss?" I've had to deal with ongoing and inherited legacy projects which run on Python 2.7, use the long-deprecated Pylons, for which there is no easy upgrade path other than a tota…

> i.e. only use the most basic and generic Django features I don't think you need to do this with Django. Features are generally very mature, stable, and are not deprecated frequently. When they are, they are deprecated years in advance with long term support still provided. In all honesty, I've seen very few projects run feature lifecycles as well as Django. I'd use everything you need to in it without concern about…

Seconded, I haven't really had many problems upgrading Django projects, and I've upgraded a lot of them.

Re: Django 3

#17

Post by darkerside »

For those on the 1.11 LTS release, and considering getting off the LTS train, I wonder whether it's a feasible upgrade path to go straight to 3.0, or if it would be smarter to go to 2.2 first.

Re: Django 3

#18

Post by sojmq »

bicx wrote: post #5

Does Python still have performance issues? That's always been my concern when considering its adoption.

Yes. If you can afford the CPU power, by all means go with Python. Otherwise just don't.

Instagram can afford it so it works fine for them. Reddit can't, so their site is always slow or down.

Re: Django 3

#20

Post by randshift »

Congrats to Django's contributors and community! It's been a while since I've actively worked in Django but I found the people in the Django ecosystem to be generally very helpful.
Post reply on HN