Barry Warsaw schrieb: > I proposed what I think is a better solution. Add > > from __future__ import unicode_strings > > to Py2.6. That would let you write Py3k compatible strings (and of > course byte literals) in 2.6. It would essential treat 'foo' as > u'foo' in the file with the future import.
I proposed a similar solution an hour ago: from __future__ import py3k_literals It's in my answer to Lennarts' posting written at 21:15 local time. Christian _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
