giumas added the comment:
It worked also for me with the official 64-bit distribution! I get that buggy
behavior with the Anaconda distribution (this was the "Library\bin").
I should have checked it as first step! My apologies and thank you so much for
your kind help.
--
resolution:
Eryk Sun added the comment:
Your example worked fine for me with the official 64-bit distribution of 2.7.10
installed in "C:\Program Files\Python27" on Windows 10. I created a junction
from "C:\Py27x64" to the 2.7 installation directory in order to run the example
as provided.
This issue
giumas added the comment:
No, I don't. I have just double-checked it.
Did you try to run my minimal example on your machine? If yes, are you getting
the same behavior?
--
___
Python tracker
Eryk Sun added the comment:
The error you're getting indicates that stdin is set to binary mode for some
reason. You can see this using the -u command line option:
C:\>py -2 -u
Python 2.7.10 (default, May 23 2015, 09:44:00)
[MSC v.1500 64 bit (AMD64)] on win32
Type "help",
New submission from giumas:
On Windows, I am getting a `SyntaxError` when I try to input commands after
having launched a Python 2.7.x interpreter with `subprocess.call`.
This is a minimal example:
import os
import subprocess
def python_env_path(python_path):