Are you saying that with that future import, b"..." is still a Unicode literal?
On Thu, Dec 8, 2011 at 6:50 PM, Lennart Regebro <rege...@gmail.com> wrote: > "from future import unicode_literals" is my fault. I'm sorry. It's > pretty useless. It was suggested by somebody and I then supported it's > adding, instead of allowing u'' which I suggested. But it doesn't > work. > > One reason is that you need to be able to say "This should be str in > Python 2, and binary in Python 3, that should be Unicode in Python 2 > and str in Python 3, and that over there should be str in both > versions", and the future import doesn't support that. > > Adding u'' support solves the problem, but then again, so does having > a b() and an u() method. I'm not sure of the utility of adding > functionality to Python 3 that can be solved with six. > > //Lennart > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
