On Sat, Feb 25, 2012 at 22:13, Guido van Rossum
<guido@python.org> wrote:
If this can encourage more projects to support Python 3 (even if it's
only 3.3 and later) and hence improve adoption of Python 3, I'm all
for it.
+1 from me for the same reasons.
* Use ``from __future__ import print_functions`` OR use ``print(x)`` but always with a single argument OR use six
* Use ``from __future__ import unicode_literals`` OR make sure to use the 'u' prefix for all Unicode strings (and then mention the concept of native strings) or use six
* Use the 'b' prefix for byte literals or use six
All understandable and with either a __future__ import solution or syntactic support solution for all issues, giving people the choice of either approach for what they prefer for each approach. I would also be willing to move the Python 2/3 compatible source section to the top and thus implicitly become the preferred way to port since people in the community have seemingly been gravitating towards that approach even without this help.
-Brett
A small quibble: I'd like to see a benchmark of a 'u' function implemented in C.
--Guido
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
--
--Guido van Rossum (python.org/~guido)