Restrict typing-extensions
package to versions before v4.6.0
#1228
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.
This PR temporarily fixes the issue described in FDS-478 where tests would fail because of using
isinstance()
in the process of executing the code as normal.From the
typing-extensions
changelog, in versionsv4.6.0
and up (released May 22, 2023 so 3 days ago):This matches the errors raised during tests when we updated our
poetry.toml
file and the dependencies in the.lock
file were allowed to update as necessary.Until our relevant classes or possibly in the python client are updated this will cause errors when we run our tests. Pinning the version gives us time to continue development on more pressing issues until we have the bandwidth to make updates to comply with the new requirements.
typing-extensions
was not a direct dependency for schematic beforehand, but was required by our dependencies so the version was relatively unlocked before this PR.