If your dependencies are satisfiable with 3.2, you're better off with 3.2. If not, use 2.7, or consider porting the dependencies yourself (assuming those dependencies have code available).
Both 2.x and 3.x are good, but 3.x is clearly the way forward. 3.x has some annoyances corrected: more central unicode, incompatible types aren't silently compared in a strange way, a callable can insist on named arguments, etc. The best way to learn the difference, IMO, is to develop on both. You can do this by using 3to2, using 2to3, or using a common subset. If you write automated tests, and set them up to run with one or more 2.x's and one or more 3.x's, you'll see the differences that matter in your code pretty quickly. I've been opting for the common subset, and have been very happy with it. Lately I'm testing on cpython 2.[567], cpython 3.[012], pypy 1.[45] and Jython 2.5.2 (the jython with a fix or two patched in). 3to2 sounds like a bit nicer option than 2to3, because 3to2 can start from code that knows the difference between the two main kinds of strings. On Thu, Jun 9, 2011 at 10:18 AM, hisan <santosh.s...@gmail.com> wrote: > Hi All, > > Please let me know which one is GOOD whether Python 2.6 OR 3.2. > Please let me know the difference between them. > Please give some refernce site or books to know the difference > -- > http://mail.python.org/mailman/listinfo/python-list >
-- http://mail.python.org/mailman/listinfo/python-list
