build: bump trio dependency to >=0.25,<1#6244
Merged
Merged
Conversation
c749d07 to
ca3440c
Compare
5 tasks
ca3440c to
52445c6
Compare
Member
Author
|
I decided to add environment markers for py>=313 and py<313 instead of bumping trio to >=0.25 on all Python versions. The reason for that is that trio>=0.25 still hasn't been packaged on many Linux distros where Streamlink is packaged. Considering that those distros also (obviously) haven't been updated to Python 3.13, only bumping trio to >=0.25 on py313+ is fine. The environment markers don't cause any issues when building Streamlink's Windows builds / Linux AppImages, so it's fine. But that's only because we set a lower version boundary, not an upper one. Pip still ignores environment markers when resolving packages on foreign platforms (e.g. building for Windows on Linux). |
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
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.
See #6243 (comment) (second issue mentioned)
There appear to be runtime issues with
trio<0.25on Python 3.13. It's not the case on Python 3.12 and below, but since we now officially support 3.13, we'll have to bump the version.Alternatively, we could add environment markers to the dependencies list, so that we could remain on
trio>=0.22,<1on Python 3.12 and below, but that can cause issues with pip's dependency resolver in certain situations, which I hate. On the other hand,trio-websocketstill hasn't published a new release with their compatibility fixes oftrio>=0.25, so making thetrio>=0.25,<1requirement now would probably introduce more packaging issues for some systems.I'll have to think about it...