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
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
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
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 l
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
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
6 matches
Mail list logo
