chore(sdk): Relax Typing Extensions Constraint #7288
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.
Description of your changes:
Typing extensions changed version scheme a couple months ago. The old schema was not semantic versioning based and was python version based. The new scheme is based on semantic versioning and moved to 4.0. 4.0+ is fully backwards compatible. So it's safe to move the bound to 5.0. And current bound unnecessarily prevents usage of some optional typing features like typeguard and pretty soon variadic types.
I would also be open to dropping upper bound entirely. It's unlikely most breaking type changes would affect normal type usage. It would heavily fracture python typing ecosystem for something core to change. And current stability focus of python devs (includes typing portion) I think it should be safe for most packages to not upper bound typing extensions. If in the future a package discovers they are affected they can add upper bound then.
Checklist: