[Python-Dev] readd u'' literal support in 3.3? (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Fri Dec 9 09:25:08 CET 2011
- Previous message: [Python-Dev] readd u'' literal support in 3.3?
- Next message: [Python-Dev] readd u'' literal support in 3.3?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
They fail to hear the "again" in that sentence. I've clearly already thought about the distinction between bytes and text at least once: that's why I'm using a u'' literal there. I shouldn't have to think about it again to service syntax constraints. Code that is more explicit than strictly necessary should not be needlessly punished.
But you don't have to think about this again, in none of the proposed alternatives (whether you use a u() function, whether you use the future import, or whether you use 2to3). They differ only (slightly) in how you spell Unicode literals, but all provide for explicit spelling of Unicode literals when applied.
Regards, Martin
- Previous message: [Python-Dev] readd u'' literal support in 3.3?
- Next message: [Python-Dev] readd u'' literal support in 3.3?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]