Well then I would go with 1.7.
Thanks for all the advise.
Happy hacking.
Krishnakant.On 11/25/2014 06:54 PM, Collin Anderson wrote:
Hi All,
If it helps, at work we have upgraded all of our websites to django 1.7,
and are only now starting to think about using migrations.
It's totally possible to use 1.7 without migrations.
It's also worth noting that although Django supports 1.6 for another 4-5
months, that's only for security fixes and data-loss bugs, whereas 1.7 gets
more bug fixes.
Collin
On Saturday, November 22, 2014 7:56:47 PM UTC-5, Thomas wrote:
On Nov 22, 2014, at 4:53 AM, Krishnakant Mane <krm...@gmail.com
<javascript:>> wrote:
Hello all,
I have been looking for some good discussion on this issue.
i see there is not much difference between 1.7 and 1.6 as far as my
requirement goes.
I have gone through the official docs for both in a kind of rappid
specific way.
As it is I am not going to use ORM at all.
I am sticking with 1.6.x in case the new migration system needs a bit of
extra time to iron out.
But since you are not using the ORM then you will not notice one way or
the other. I’d probably go with 1.7.x…
hth
- Tom
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/5474DC47.9000605%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
