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/2009-October/092928.html below:

[Python-Dev] Initialization of __builtins__

[Python-Dev] Initialization of __builtins__ [Python-Dev] Initialization of __builtins__Eric Smith eric at trueblade.com
Sat Oct 10 22:29:26 CEST 2009
Vinay Sajip wrote:
> If __builtins__ is an implementation detail which can't be relied on, should the
> py3k code be changed to the try: form? Or shall I just remove the checks
> altogether, since Unicode should always be there in 3.x?

Remember that the identifier "unicode" isn't present in py3k. There it's 
"str" and it holds Unicode strings.

Unless you're trying to keep the code identical in both branches, I'd 
just remove the check in py3k and assume str is what you always want to use.

Eric.


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