fix: do not coerce StringIO into str#3
Merged
DonDebonair merged 1 commit intoJul 11, 2026
Conversation
A recent commit to pyinfra introduces `io:<string content>` as a way to pass StringIO objects to operations in test fixtures. pyinfra-testing did not support this yet. Now it does.
DonDebonair
force-pushed
the
fix/support-io-stream-args
branch
from
July 3, 2026 17:32
7953f8d to
1d74c2a
Compare
Fizzadar
approved these changes
Jul 6, 2026
Collaborator
Author
|
Will you merge and publish a new version @Fizzadar? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A recent commit to pyinfra introduces
io:<string content>as a way to pass StringIO objects to operations in test fixtures. pyinfra-testing did not support this yet. Now it does.