is it worth going for version 1.6 for commertial project
70 views
Skip to first unread message
Krishnakant Mane
Nov 22, 2014, 7:53:42 AM11/22/14
to django...@googlegroups.com
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 mainly intrested in views which will talk to an already existing
core logic written as an xmlrpc server.
The code is stable and works excelent on commertial projects.
My main interest is to just build the web front end (I would be using
views and templates ) for the said project.
I like the templating system and the forms are handled very well.
I would be further interested in the way Django helps write css or
integrate javascript libraries like Bootstrap using Python code itself.
So I don't see any great difference in 1.6 vs 1.7, provided I have not
missed some thing.
The question is now, given that support for 1.6 could be over soon, is
it worth while to stick with it?
on the other hand, 1.7 will also loose out support some tiem or the
other, although later as compared to version 1.6? Again, 1.6 I guess
will receive updates at least for a year if I am not mistaken?
I use Python 2.7 so no problems on that department.
Kindly let me know your views so that I can take a decision at the earlist.
happy hacking.
Krishnakant.
Are theredevelopers on this list who still vouch by 1.6 and would
recommend me to go with that version?
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 mainly intrested in views which will talk to an already existing
core logic written as an xmlrpc server.
The code is stable and works excelent on commertial projects.
My main interest is to just build the web front end (I would be using
views and templates ) for the said project.
I like the templating system and the forms are handled very well.
I would be further interested in the way Django helps write css or
integrate javascript libraries like Bootstrap using Python code itself.
So I don't see any great difference in 1.6 vs 1.7, provided I have not
missed some thing.
The question is now, given that support for 1.6 could be over soon, is
it worth while to stick with it?
on the other hand, 1.7 will also loose out support some tiem or the
other, although later as compared to version 1.6? Again, 1.6 I guess
will receive updates at least for a year if I am not mistaken?
I use Python 2.7 so no problems on that department.
Kindly let me know your views so that I can take a decision at the earlist.
happy hacking.
Krishnakant.
Are theredevelopers on this list who still vouch by 1.6 and would
recommend me to go with that version?
Tom Lockhart
Nov 22, 2014, 7:56:47 PM11/22/14
to django...@googlegroups.com
On Nov 22, 2014, at 4:53 AM, Krishnakant Mane <krm...@gmail.com> 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.
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
Collin Anderson
Nov 25, 2014, 8:24:44 AM11/25/14
to django...@googlegroups.com
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
George Silva
Nov 25, 2014, 8:34:02 AM11/25/14
to django-users
I'm using the new migrations system with a production system and it's been great.
No complaint at all.--
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...@googlegroups.com.
To post to this group, send email to django...@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/512ad969-af3b-445f-954c-b669674181f4%40googlegroups.com.
--
George R. C. Silva
SIGMA Consultoria
SIGMA Consultoria
----------------------------
Krishnakant Mane
Nov 25, 2014, 2:46:03 PM11/25/14
to django...@googlegroups.com
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
> 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
Reply all
Reply to author
Forward
0 new messages