-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 20, 2008, at 2:48 AM, Lennart Regebro wrote:
> So, please allow u'' in Python 3.0! With that change, my > porting/compatibility worried would be gone, and you would be able to > choose between the three porting strategies dependningon how your code > base and user base looks: 1. Clean break. 2. Syncing with 2to3, 3. > Supporting both 2.6 and 3.0. 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. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR+LQPXEjvBPtnXfVAQL1igP+LFAJyXhSs9qbW8dcOvRhvlAeSNGKdQ8h pMP3QWXY1TlVNs+3UQF93neL+TSSc1AN1iOIg42VRQefBZPaOTnnbtYSWwyYXW4o ITYpaXS8h5wwpvqXRawGGaIaeS/t1/xMEqfIHbhHeFyrbRbfk1JEn5aDSz3A7gIW kwbYdNAaqGo= =X4nr -----END PGP SIGNATURE----- _______________________________________________ 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
