Repository navigation
Always erase last known value from instances when using binder or partial types - #7354
Merged
Merged
Conversation
added 2 commits
August 16, 2019 18:47
ilevkivskyi
changed the title
Member
Author
|
Hm, this is one more case when binder and partial types share bugs. Looks like another argument in favour of trying to combine them. |
JukkaL
added a commit
that referenced
this pull request
Feb 22, 2022
JukkaL
added a commit
that referenced
this pull request
Feb 22, 2022
…7354) (#12239) Fixes some regressions. Context: python/typeshed#7258
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
2 participants
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 the test cases for simplified example of currently problematic behaviour when using
--strict-equality.