1.8 or 1.9?

[Ankush Thakur]

I want to take a Udemy course on Django because it shows how to make an e-commerce website. The only catch - it follows Django 1.8. So my question is: Will I be "wasting" my time learning a possibly outdated (or unrecommended) version of Django? I have a feeling the changes aren't going to be that significant, but later on when I recreate the project myself in 1.9, I wouldn't want to tear out my hair solving weird error messages.

Any wise words?

Regards,

Ankush Thakur

[Sean McKinley]

I haven't taken the course, but the differences between basic Django 1.8 and 1.9 are not all that significant and you can find out if you are being taught something odd by reviewing 1.9 release notes. Big caveat, syncdb is gone in 1.9 so you have to learn migrations if the Udemy course is using syncdb.

[Florian Schweikert]

On 12/05/16 18:36, Sean McKinley wrote:
> I haven't taken the course, but the differences between basic Django 1.8
> and 1.9 are not all that significant and you can find out if you are
> being taught something odd by reviewing 1.9 release notes. Big caveat,
> syncdb is gone in 1.9 so you have to learn migrations if the Udemy
> course is using syncdb.

syncdb was deprecated in 1.7, with release of the django migrations.
So basically the only difference may be using another command for the
same thing.
If there are no deprecation warnings using the app with 1.8 it should be
no problem to upgrade to 1.9.
The main difference between 1.8 and 1.9 in my opinion is support.
1.8 is LTS and will be supported longer than 1.9, we still build all new
applications for our customers with 1.8 at work because of the longer
support.
Most of the features of 1.9 are possible to install as python package,
like the new admin theme and PermissionMixins/django-braces

Upgrading a minor version is mostly easy and a good thing to learn ;)

--
Florian

[dk]

will be better to  hit your head vs the wall now using 1.9, 

than later in a real project,    plus there is not much difference, they added a couple of things,  but mostly is the same,  I would do the Django tutorial of Django website before, step by step.

On Thursday, May 12, 2016 at 8:55:15 AM UTC-7, Ankush Thakur wrote:

[Ankush Thakur]

Thank you, Florian! :-)

Indeed, stability and job market are what's on my mind. It's comforting to know what I can stick to LTS versions and be assured of (almost 100%) stability. Just another minor concern: What if, say, the other minor upgrade rolls out a really cool feature that takes out a lot of pain than when performing certain tasks in 1.8? I hope it won't feel like I'm stuck with maintaining VB code while the world has moved on? :P

Best,

Ankush

[Ankush Thakur]

I've done the official tutorial and the Django Girls tutorial (I like the latter better ^.^) but now want to learn to build something nontrivial. I saw a thread on Reddit that talked about frustrations arising from minor inconsistencies between libraries and non-LTS releases. What would be your thoughts on that?