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

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

Compiler treats None both as a constant and variable

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

"Raymond Hettinger" <raymond.hettinger@verizon.net> wrote in message
news:002001c2f636$77ad2ce0$e60ca044@oemcomputer...
> >>> 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?

If one understands (as I do) the default return 'None' to mean the
singleton NoneType object that the name 'None' is assumed to be bound
to in the docs and which it is bound to on startup, then no.

> Should the compiler use the GLOBAL in both places?
> Or, is it reasonable to use CONST in both places?

I understood the latter to be the plan after a sufficient warning
period.

TJR

• Previous message: [Python-Dev] Compiler treats None both as a constant and variable
• Next message: [Python-Dev] 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