This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-09-20.22:46:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474411584.76.0.142913930665.issue28217@psf.upfronthosting.co.za>
In-reply-to
Content
Here's the ctypes code (mentioned on issue 1602) for writing to the input buffer and reading from the screen buffer. For output testing I also have a context manager to create and temporarily activate a new screen buffer with a given number of columns and rows and filled with a particular character (e.g. NUL), which makes it easier to read the output up to the current cursor position. 

Activating the new screen can be factored out if you're just testing a child writing to stdout. I added the screen activation part in order to read the output from a program that was stubbornly writing to CONOUT$, ignoring the pipe that was passed as stdout.
History
Date User Action Args
2016-09-20 22:46:24eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower
2016-09-20 22:46:24eryksunsetmessageid: <1474411584.76.0.142913930665.issue28217@psf.upfronthosting.co.za>
2016-09-20 22:46:24eryksunlinkissue28217 messages
2016-09-20 22:46:24eryksuncreate