Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use Bytes/StringIO for pipes #49

Merged
merged 3 commits into from
Aug 18, 2021
Merged

use Bytes/StringIO for pipes #49

merged 3 commits into from
Aug 18, 2021

Conversation

minrk
Copy link
Owner

@minrk minrk commented Aug 18, 2021

avoids buffer size issues (closes #48)

backward compatibility issue: before this, output could be read while inside the context manager, (and must be for large output to avoid blocking) while after it can only be read reliably after the context has finished.

We could try to use a more sophisticated approach that preserves both - infinite buffer size and safe read/write order, but this is the simplest fix that I think should work in all real-world cases.

@minrk minrk force-pushed the full-buffers branch 2 times, most recently from a8bdfc9 to ad12d14 Compare August 18, 2021 10:33
avoids buffer size issues

backward compatibility issue: before this, output could be read while inside the context manager,
(and must be for large output to avoid blocking)
while after it can only be read reliably after the context has finished
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

wurlitzer.pipes hang if output from C is very large
1 participant