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

Showing content from https://mail.python.org/pipermail/python-dev/2003-March/034281.html below:

[Python-Dev] Compiler treats None both as a constant and variable

• Previous message: [Python-Dev] Re: Fast access to __builtins__
• Next message: [Python-Dev] Re: Compiler treats None both as a constant and variable
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>> def f():
 None  

>>> dis(f)
2           0 LOAD_GLOBAL              0 (None)
              3 POP_TOP             
              4 LOAD_CONST               0 (None)
              7 RETURN_VALUE 

>>> None = 1
<stdin>:1: SyntaxWarning: assignment to None
>>> f() == None
False


Is this a bug?
Should the compiler use the GLOBAL in both places?
Or, is it reasonable to use CONST in both places?


Raymond Hettinger

• Previous message: [Python-Dev] Re: Fast access to __builtins__
• Next message: [Python-Dev] Re: Compiler treats None both as a constant and variable
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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