A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2009-January/084833.html below:

[Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3?

[Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3? [Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3?Benjamin Peterson benjamin at python.org
Mon Jan 5 00:53:43 CET 2009
On Sun, Jan 4, 2009 at 5:36 PM,  <skip at pobox.com> wrote:
>
>    >> Since print is now a builtin function why is there still a PRINT_EXPR
>    >> opcode?
>
>    Benjamin> I believe it's used in the interactive interpreter to display
>    Benjamin> the repr of an expression.
>
> Wouldn't it make more sense for the interactive interpreter to call
>
>    print(repr(expr))

I'm not sure about the reasoning for keeping PRINT_EXPR alive. When I
look at the code of PyRun_InteractiveOne, it seems it should be
possible to kill it off.


-- 
Regards,
Benjamin
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