[issue29037] Python 2.7.13 prints version header and exits immediately on Windows 10 x64
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", "copyright", "credits" or "license" for more information. >>> """ -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29037> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29037] Python 2.7.13 prints version header and exits immediately on Windows 10 x64
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 <rep...@bugs.python.org> <http://bugs.python.org/issue29037> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29037] Python 2.7.13 prints version header and exits immediately on Windows 10 x64
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 the previous Python (2.7.12) so as to make sure none of them was the cause of the problem. That unfortunately did not affect the buggy behavior. -- Added file: http://bugs.python.org/file46064/python-v.txt ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29037> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29037] Python 2.7.13 prints version header and exits immediately on Windows 10 x64
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". -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29037> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29037] Python 2.7.13 prints version header and exits immediately on Windows 10 x64
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, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. E:\Users\thisuser> """ This did not happen before. The same happens when Python is run from a powershell. I have no problems running ipython or jupyter notebook, however. And Python does the right thing when run under MSYS2, like so: """ $ python -i Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> """ Could this be an encoding problem? Because MSYS2 is fairly new and I think it might be more friendly to the encoding issues related to Windows shell programming. -- components: Windows messages: 283773 nosy: abkhd, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Python 2.7.13 prints version header and exits immediately on Windows 10 x64 versions: Python 2.7 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29037> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
