A
A
andyN2012-05-12 09:03:52
Django
andyN, 2012-05-12 09:03:52

Django: does it make sense to migrate to 1.4 from 1.2?

Situation: there is a prototype of one project written for version 1.2. Does it make sense to rewrite it for the new version 1.4? Yes, I read the list of changes, but none of them are vital.
That is, if it is quite formal, then the questions are as follows:
1) in your opinion, is it necessary to switch?
2) if yes, why?
3) how much code will have to be rewritten?
4) what do you personally like in 1.4 (which is not in 1.2).
Thank you.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
V
VBart, 2012-05-12
@VBart

If it is assumed that the project is alive, then it makes sense to switch to the current and supported version because it is up-to-date and supported. =)
I've never seen a lot of code rewritten when going from 1.x to 1.(x+1). Usually purely formal changes are required. Yes, you yourself should know better about your own project, and read the changelog. And the longer you wait, the more such changes will accumulate, both in your project and due to the release of even later versions of janga. In the end, in some next version there will be changes that you really need, but it will become really difficult to switch to it.

3
3ds, 2012-05-18
@3ds

I can’t say for sure, but I switched almost without any changes at all. Passed just because of timezone support - och. handy thing. Well, in general, I advise you to go :)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question