Thanks for the comment.
First and foremost, I never called anyone stupid.
eBooks and paper books are not version of books, it cannot be compared at all. Book editions can be compared though, you should always go with newer editions of books, they have been edited, mistakes has been taken care of and new materials can be found there too.
The whole teaching or how to do it has been described on Python Wiki page already. Many major libraries also have been upgraded to latest recently.
“Python 2” is legacy code, doesn’t matter of you accept or deny it, it’s not a language, it’s a version of “Python” language itself.
You should never ever stick with legacy version, unless you have to and there’s no other way around it, like vendor locks, SDKs or a bleeding third party library that is really really important and upgrading would not be suitable.
If we’re going to continue in this direction, Someday we might have to use another tool to write a language with a syntax like Python to produce “Python 2” and “Python 3” compatible source and later supports “Python 4”, people won’t be writing “Python” anymore but a language like “Python” that compile or transpile something that different Python implementation will run it.
That time we gonna think about a language that compiles to something to be runnable on:
- Python 2
- Python 3
- Python 4
Having a distance between “Python 2” and “Python 3” will might end up in a situation like that.
Who knows, something like like
2to3 might be just a start for tools like that.