Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
How much are you going to study.
If a couple of years, then the third - because probably a large (if not most) part of the libraries and solutions will switch to it during this time. If you plan to master it in a month or two, then 2.6 \ 2.7 - because now most of them are written and, accordingly, most of the libraries and solutions are on it. :)
Why a python at all?
There are a bunch of other wonderful languages - not for the sake of holivar, but what are you going to do in it?
From the direction of activity, you need to choose the language,
and its version, respectively.
Well, to the heap - having studied any of the pythons, you will easily perceive the code on any other versions
- however, after reading a little about the differences (there are not so many of them, by the way).
However, without a lot of correct examples, it will be difficult for you to feel
all the delights of the new constructions that appeared in 3. * in relation to 2.6 \ 2.7.
Of course, the last one. 3.3.
The transition from the 2* branch is quite slow, but stable. The same Django 1.4 has beta support for the third python.
Read books/documentation on version 3. There will be written about the new beautiful and the differences from the 2nd version are indicated.
Weird question. Of course, the last one. In a specific project and environment, the restrictions of 2.7 will make themselves felt, but there is nothing wrong with that. And knowing the capabilities of the latest version is always useful.
Mark Lutz's book, Learning Python, deals with both branches at once, detailing the differences, although there is some emphasis on 3.x.
hmm, I would start thinking like this:
depending on which direction you will use it later, if you want to use it on the Web (Django, Flask ...) then it’s better to choose 2.7, there will be fewer problems with it (well, for example, Django with 3 branch is not yet it works properly, although recently a new one has been decided, support for 3 branches is declared there) ...
and if you are just starting to get acquainted with this PL, then 2.7 is better, you can then adapt to version 3 ... (IMHO)
I recommend learning 2.7 now everyone is using it. Active movements towards the third branch are not visible. Some libraries and frameworks are porting to 3, but most still work on 2.5-2.7. I don't think things will change in the next couple of years. The same Flask is not going to be transferred to 3. I am not aware of large projects working on the third python, although I do not exclude that they exist.
It looks like the python way now is that you need to know both versions.
As it was two years ago, so it will be two more years.
If the task is "development and self-study" - then of course the third version, if the task is "find a job and earn money" - then the second (but with an eye on the third), because. in real projects, you will rely on third-party libraries, most of which do not have a version for the third python.
To begin with, I would look at the difference in the branches - what is removed, what is added, what is changed, because it is unlikely that many basic things will differ very much from version to version, the operators are the same, but the libraries, especially in third-party applications can indeed be tied to a specific branch.
I also asked myself this question recently. I read the habr, started with the third version, then, after some time, I decided to look at the list of vacancies for the sake of interest, and version 2. * is indicated everywhere in the requirements. I thought and thought, and now I have several books - a basic one about the second version, and an additional one about the third. I read, then in one I will find something useful, then in the other. That's how we live.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question