On Sun, Apr 17, 2016 at 11:13 AM, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote: > On Sat, 16 Apr 2016 21:59:01 -0400, Random832 <random...@fastmail.com> > declaimed the following: >> >>I heard Windows 10 is going to finally fix this, anyway. > > Probably by removing the old CLI window completely and making everyone > learn PowerShell ISE
PowerShell ISE doesn't support interactive console applications. It runs console apps with a hidden console (conhost.exe) and sets the StandardOutput and StandardError to pipes. It leaves StandardInput set to the console input handle. If you run python.exe in this environment, you can use ctypes to show the console. Then enter commands in the console, and get the output in ISE. Or rebind sys.stdout and sys.stderr to \\.\CONOUT$ handles and forget about ISE, which is really only meant for developing PowerShell scripts. Microsoft won't abandon existing console programs, such as python.exe. The console system was fairly stagnant between NT 4 and Vista. In Windows 7, they changed how it interacts with a Windows session, by moving the server out of csrss.exe to multiple conhost.exe instances. In Windows 8, they reimplemented the API to use a kernel device driver, condrv.sys. For Windows 10, they've focused on improving the user interface: https://blogs.windows.com/buildingapps/2014/10/07/ console-improvements-in-the-windows-10-technical-preview There's a new blog dedicated to Windows command-line tools, which should be the place to look for announcements about the console subsystem and the new Linux command-line environment that depends on the console: https://blogs.msdn.microsoft.com/commandline -- https://mail.python.org/mailman/listinfo/python-list
