"from future import print_function" was added to the test file but
not to the embedded interpreter. This change uses file.write instead to
avoid all problems with print.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Can you leave the from future import print_function at the top? That's
orthogonal to changing the dynamically executed code.
I can reproduce this problem by running LLDB in 2.7 and entering the
embedded interpreter and typing print("foo", file=sys.stdout). So I can
probably fix that and this is an ok workaround for now, but people still
need to be using print function instead of print statement on statically
generated python code, so I think the future statement should stay.