You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some code with uses subprocess with a file handle as the stdout argument. The subprocess module will write the output of the command to the file handle, and my code does not directly call communicate. When I register a command with fake_process in the tests with some stdout content specified, the file doesn't seem to have the expected content written to it. Have I overlooked something, or is that not supported by this library?
I've missed that use case, it's not supported right now. I think it could be done currently by using the callback function, but it would be quite clunky.
I'll fix the code to support this feature soon. Thanks for reporting.
I have some code with uses
subprocess
with a file handle as thestdout
argument. Thesubprocess
module will write the output of the command to the file handle, and my code does not directly callcommunicate
. When I register a command withfake_process
in the tests with somestdout
content specified, the file doesn't seem to have the expected content written to it. Have I overlooked something, or is that not supported by this library?Example:
Result:
The text was updated successfully, but these errors were encountered: