Update dependency typing_extensions to v4.7.0#40
Merged
Conversation
🎉 Happy commit!
|
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #40 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 4 4
Lines 56 56
=========================================
Hits 56 56
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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
1 participant
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 contains the following updates:
4.6.3->4.7.0Release Notes
python/typing_extensions (typing_extensions)
v4.7.0Compare Source
which reaches its end of life on June 27, 2023. Version 4.8.0 will support
only Python 3.8.0 and up.
typing_extensions.Protocolclass that had one or morenon-callable members would raise
TypeErrorwhenissubclass()was called against it, even if it defined a custom
__subclasshook__method. The correct behaviour -- which has now been restored -- is not to
raise
TypeErrorin these situations if a custom__subclasshook__methodis defined. Patch by Alex Waygood (backporthttps://github.com/python/cpython/pull/105976l/105976).
Configuration
📅 Schedule: Branch creation - "before 9am every weekday,every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.