Hi Jamal, I agree with what you say here. Also most of the books you read about Python would have code that you would not need to change for 3.0 or 2.6. Jim ---------- Jim Homme, Usability Engineering. 412-544-1810. Note: I will reply to email and voice mail within four hours. "Nothing in this world can take the place of persistence. "Talent will not; nothing is more common than unsuccessful people with talent. "Genius will not; unrewarded genius is almost a proverb. "Education will not; the world is full of educated derelicts. "Persistence and determination alone are omnipotent." - Calvin Coolidge (1872-1933) -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui Sent: Thursday, June 18, 2009 6:18 AM To: ProgrammingBlind@xxxxxxxxxxxxx Subject: Python 2.5 To any beginning Python programmers, this is the version I recommend using rather than 2.6 or 3.x. If you know what you are doing and have a specific need to use the later versions, then go for it. Otherwise, you will probably encounter compatibility problems with popular 3rd party Python libraries, including py2exe -- the one that lets you create independent executables on Windows. In my opinion, there is almost no functionality that one loses by using 2.5 at this time. 2.6 and 3.x are mainly a matter of syntax changes and re-organization of built-in modules so far. This is not a disapproval of the direction the Python language is going -- just a reality check on what is working well at present, so beginners can minimize headaches. Jamal __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.