build: set trio min-requirement back to 0.22 #5902
Merged
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.
strict_exception_groups=TrueinCDPClient.launch()trio.run()early in Streamlink's testsThis lifts the dependency requirements of Streamlink a bit. I didn't want to do this initially and bumped trio to
>=0.25in #5895, because it requires patchingtrio.run()in Streamlink's tests, aspytest-triodoesn't allow setting customtrio.run()args/kwargs.Since packagers of some Linux distros like Debian have to apply the same kind of patch in order to package Streamlink 6.7.1, we should instead apply the version compatibility fixes here ourselves.