[Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3? (original) (raw)
Benjamin Peterson benjamin at python.org
Mon Jan 5 00:53:43 CET 2009
- Previous message: [Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3?
- Next message: [Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 PRINTEXPR >> 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
- Previous message: [Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3?
- Next message: [Python-Dev] Why is there still a PRINT_EXPR opcode in Python 3?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]