[3.7] bpo-28866: No type cache for types with specialized mro, invalidation is hard. (GH-13157)#13589
Merged
miss-islington merged 1 commit intopython:3.7from May 26, 2019
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
No type cache for types with specialized mro, invalidation is hard.
FIX: Don't disable method cache custom types that do not implement mro().
fixing implem.
Avoid storing error flags, also decref.
news entry
Clear as soon as we're getting an error.
FIX: Reference leak.
(cherry picked from commit 180dc1b)
Co-authored-by: Julien Palard julien@palard.fr
https://bugs.python.org/issue28866