Message277078
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. |
|
Date |
User |
Action |
Args |
2016-09-20 22:46:24 | eryksun | set | recipients:
+ eryksun, paul.moore, tim.golden, zach.ware, steve.dower |
2016-09-20 22:46:24 | eryksun | set | messageid: <1474411584.76.0.142913930665.issue28217@psf.upfronthosting.co.za> |
2016-09-20 22:46:24 | eryksun | link | issue28217 messages |
2016-09-20 22:46:24 | eryksun | create | |
|