ensure recursion guard is always used as a stack #1166
Merged
+137
−97
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.
Change Summary
Introduces
RecursionGuard
as a type which goes in a function frame and releases on drop.This fixes the issue seen updating to 2.16.0.
Because
RecursionGuard
takes ownership of the state, it guarantees that two guards can't overlap their usage of the state.Related issue number
Checklist
pydantic-core
(except for expected changes)