A.B., Khalid added the comment:
OK. I updated pyreadline to version 2.1 from version 2.0 and now the buggy
behavior is gone.
"""
E:\>python
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit
(AMD64)] on win32
Type "help", "copyr
A.B., Khalid added the comment:
Output of SET PY is as follows:
E:\>SET PY
PYSDL2_DLL_PATH=E:\Python27\Lib\site-packages
PYTHON3_HOME=E:\Python35
PYTHON_HOME=E:\Python27
--
___
Python tracker
<http://bugs.python.org/issu
A.B., Khalid added the comment:
I enclose the output of "python -v". Where Python exits is of course indicated
by the end of the file. However, there is no obvious error that is printed out.
Also it might be worthwhile to note that I cleared all compiled files left over
from th
A.B., Khalid added the comment:
Running "where python" shows that the updated python (the one with the bug
mentioned above) is the one being run.
Running python -c "import sys; print sys.stdin.isatty()" prints out "True".
--
New submission from A.B., Khalid:
I updated my Python 2.7.12 to 2.7.13 on Windows 10 x64. When I run it in
Windows command prompt shell, Python prints the version header and then exits
immediately. Like so:
"""
E:\Users\thisuser>python
Python 2.7.13 (v2.7.13:a06454b1afa1,
