A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-December/114815.html below:

[Python-Dev] readd u'' literal support in 3.3?

[Python-Dev] readd u'' literal support in 3.3? [Python-Dev] readd u'' literal support in 3.3?"Martin v. Löwis" martin at v.loewis.de
Fri Dec 9 09:25:08 CET 2011
 > 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

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4