Prev: how to determine whether pathname1 is below bathname2
Next: Why doesn't python's list append() method return the list itself?
From: Zooko O'Whielacronx on 11 Jul 2010 10:45
Folks:

I have been (I admit it) a Python 3 skeptic. I even speculated that
the Python 3 backward-incompatibility would lead to the obsolescence
of Python:

http://pubgrid.tahoe-lafs.org/uri/URI:DIR2-RO:ixqhc4kdbjxc7o65xjnveoewym:5x6lwoxghrd5rxhwunzavft2qygfkt27oj3fbxlq4c6p45z5uneq/blog.html

However, things are really looking up now because it turns out that it
is eminently practical to support both Python 2 and Python 3 with a
single codebase.

There have been some recent discussions about that on this list. A few
references:

http://mail.python.org/pipermail/python-list/2010-July/1249312.html
http://www.voidspace.org.uk/python/weblog/arch_d7_2010_03_20.shtml#e1167
http://nedbatchelder.com/blog/200910/running_the_same_code_on_python_2x_and_3x.html
http://www.mail-archive.com/numpy-discussion(a)scipy.org/msg26524.html

Benjamin Peterson has even written a library intended to help
programmers who want to do that:

http://packages.python.org/six/

This note to the list is to express my wish for an automated tool
named "2to6" which converts my Python 2.6 codebase to being both py2-
and py2- compatible using Benjamin Peterson's six library.

Regards,

Zooko
 | 
Pages: 1
Prev: how to determine whether pathname1 is below bathname2
Next: Why doesn't python's list append() method return the list itself?