fix 'maximum recursion depth is exceeded' for sqlalchemy objects#165
Closed
the-vty wants to merge 1 commit intosamuelcolvin:mainfrom
Closed
fix 'maximum recursion depth is exceeded' for sqlalchemy objects#165the-vty wants to merge 1 commit intosamuelcolvin:mainfrom
the-vty wants to merge 1 commit intosamuelcolvin:mainfrom
Conversation
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 allows to dump SQLAlchemy objects with the reference cycle. If a circular reference is detected it displays "<visited Table(id=$primary_key_value)>"
Also it skips "awaitable_attrs" (an internal SA attribute)