I already bought a good book on Python 2.5. Should I return it and get a book on 3.1 instead? that I know this question has already been asked, but I wanted a more up-to-date answer.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I already bought a good book on Python 2.5. Should I return it and get a book on 3.1 instead? that I know this question has already been asked, but I wanted a more up-to-date answer.
Linky: Python2orPython3
Synopsis:
Python 2.5 is old but the general consensus is Python 3 if you don’t have any dependencies or a large code base already in production, if this is the case then writing more future ready code might be a better option. On the other hand bigger projects have already started the long process of porting their code.
When you learn python really you should learn 2 and 3 and then just remember the differences between them. Its not like a different language all together and you could probably get most of the differences on a cheat sheet.