Should I switch to python3?

Question

Django

Should I switch in my projects to python3 from the 2nd? Although on the other hand we will all be there ...

Answer 1

Yes.

Answer 2

If these are web application projects built on dependencies that are still not ported to 3, then you should not switch, if these are applications themselves (reusable apps), then you definitely need to be compatible with 2, 3 versions of python.

Answer 3

I can just percentage, as Mark Lutz answered this question in his book :
"whether to switch to Python 3 or not depends on your goals. Many large projects are written many years ago, have a huge number of lines of code. Nobody is going to rewrite them. So to maintain such projects, you will need to know the features of Python 2.x. New projects still try to write under Python 3.x."
For my projects, I also try to choose Python 3.x - why force the newly-come generation to understand the intricacies of the "outgoing" one.

Answer 4

In the third yummy, only asyncio. Everything else is not such an improvement.
I'm sticking with 2k for now - the benefits from Pypy - outweigh the thought that sooner or later I'll need to switch to a third branch.

Answer 5

Yes.

Answer 6

For my projects, python 3 is still better. On the one hand, I agree with Mr. raiboon - in the second branch, you have to fuss with threads and processes, while in the third there is a good asynchrony. Plus - a little ennobled syntax. But for production, I would also think - as far as I remember, asyncio has not yet left beta and can change, and although there are fewer problems with porting libraries, they have not completely disappeared yet. But the problem with Pypy, which was raised by Mr. raiboon , is not so acute in production - I have not seen Pypy in production yet (but, probably, it is somewhere).

Answer 7

Here is what they say about this at the office. site. Link