With version 3.3 Python had introduced Python Launcher for Windows. In short (and adhering to my use case), when a Python script with a shebang like #!/usr/bin/env python3 is launched on Windows, it is in fact launched by py.exe, which, in turn, launches the appropriate Python interpreter, just as the image below demonstrates (this script was launched implicitly, like this: py_test1.py):
This might put ConEmu to complexities with hooks. Things I observe for already a long time is that the output of such script (both stdout and stderr) don't make it to the buffer maintained by ConEmu Far plugin (the one displayed with "View/Edit console output"), which is very inconvenient when the output takes more than one screen.
I should add that in this particular case ConEmu is run with its "Alternative" and "BufferHeight" modes off. Also, the output is captured right if I run the same script explicitly, like this: py C:\Programs\scripts\py_test1.py, though this time the process tree differs a bit:
Another ConEmuC.exe process is prepended to py.exe when run this way. Maybe things should be handled the same way for implicit runs too?
The text was updated successfully, but these errors were encountered:
…ociated with `py.exe`
The script is executed by Far3 via ShellExecuteEx(script.py),
which in turn runs CreateProcess(py.exe, script.py) in background thread
…ociated with `py.exe`
The script is executed by Far3 via ShellExecuteEx(script.py),
which in turn runs CreateProcess(py.exe, script.py) in background thread
ConEmu 170807 [32]
OsVer: 6.3.9600.x32, Product: 1, SP: 0.0, Suite: 0x100, SM_SERVERR2: 0
Python 3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:38:22) [MSC v.1600 32 bit (Intel)] on win32
Probably related: #546, #457
With version 3.3 Python had introduced Python Launcher for Windows. In short (and adhering to my use case), when a Python script with a shebang like
#!/usr/bin/env python3
is launched on Windows, it is in fact launched bypy.exe
, which, in turn, launches the appropriate Python interpreter, just as the image below demonstrates (this script was launched implicitly, like this:py_test1.py
):This might put ConEmu to complexities with hooks. Things I observe for already a long time is that the output of such script (both stdout and stderr) don't make it to the buffer maintained by
ConEmu Far plugin
(the one displayed with "View/Edit console output"), which is very inconvenient when the output takes more than one screen.I should add that in this particular case ConEmu is run with its "Alternative" and "BufferHeight" modes off. Also, the output is captured right if I run the same script explicitly, like this:
py C:\Programs\scripts\py_test1.py
, though this time the process tree differs a bit:Another
ConEmuC.exe
process is prepended topy.exe
when run this way. Maybe things should be handled the same way for implicit runs too?The text was updated successfully, but these errors were encountered: