Title: Embedding should have public API for interactive mode
Type: Stage:
Components: Interpreter Core Versions: Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: nanjekyejoannah, steveire, vstinner
Priority: normal Keywords:

Created on 2017-07-11 14:34 by steveire, last changed 2019-06-21 14:30 by nanjekyejoannah.

Messages (1)
msg298162 - (view) Author: Stephen Kelly (steveire) Date: 2017-07-11 14:34
Consider the following three snippets:


const char* sourceCode = 
    "a = 9\n"
// This is OK! Python runs both lines.
// BUT: The value of 'a' is not printed
PyRun_StringFlags(sourceCode, Py_file_input, localDictionary, localDictionary, 0);


// This is OK! We run one statement at a time:
PyRun_StringFlags("a = 9", Py_single_input, localDictionary, localDictionary, 0);
// Python prints the value of 'a' because we use Py_single_input!
PyRun_StringFlags("a", Py_single_input, localDictionary, localDictionary, 0);


const char* sourceCode = 
    "a = 9\n"
// This is NOT OK! Python throws a SyntaxError because we used Py_single_input.
PyRun_StringFlags(sourceCode, Py_single_input, localDictionary, localDictionary, 0);

The intention is to be able to run script code in an interpreter built into an application, and to maintain two user features:

1) The behavior is the same as the standard python interpreter with regard to printing values automatically without requiring the print() statement.
2) It is allowed to copy/paste possibly multiple lines/statements and execute them

These two requirements are in conflict, because while Py_single_input enables the first, it forbids the second.

I have worked around this by using internal API in Python-ast.h and setting `mod->kind = Interactive_kind;` before calling `PyAST_CompileEx`, but that should not be needed.
Date User Action Args
2019-06-21 14:30:56nanjekyejoannahsetnosy: + nanjekyejoannah
2019-05-15 02:34:37vstinnersetnosy: + vstinner
2017-07-11 14:34:17steveirecreate