Reply to thread

Message: [QUOTE="Dave Angel, post: 3857738"] The usual rule in debugging: split the problem into two parts, and test each one separately, starting with the one you think most likely to be the culprit In this case the obvious place to split is with the data you're passing to the communicate call. I expect it's already wrong, long before you hand it to the subprocess. So write it to a file instead, and inspect it with a binary file viewer. And of course test it manually with your validate program. Is validate really expecting a Unicode stream in stdin ? [/QUOTE]