It must be 3, 2 is already stable (not updated). Whenever they encounter this problem, many people will say "many modules do not support 3", but 3 has been released for more than 5 years. After 5 years, it has not supported new versions of modules, and maintenance has basically stopped.

The first sentence above said that the grammatical changes were not major, but later said that the version changes were too big. Don't you feel contradictory?

Nowadays, it is not common to encounter the "important but not supported" third-party package problem, unless you have very special needs. Many people are unwilling to use 3. I think they are just lazy, just like they are unwilling to replace .

Even if you really encounter an important package that only supports 2, that is not a problem. You can install both 3.4 and 2.7, and then run with different versions. Even projects that require cross-use are not a problem. Python claims to be able to glue different languages ??together. There is no reason why it cannot glue different versions of itself together.

The important thing is to avoid writing code that only runs on 2