Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Revisit cases where __pydantic_private__ is None vs {} #9282

Open
sydney-runkle opened this issue Apr 19, 2024 · 0 comments
Open

Revisit cases where __pydantic_private__ is None vs {} #9282

sydney-runkle opened this issue Apr 19, 2024 · 0 comments

Comments

@sydney-runkle
Copy link
Member

As seen in #9168, there are some cases where __pydantic_private__ is set to None, and others where it's an empty dict - I'd like to further investigate these situations - I know we fixed a bug in pydantic-core related to this recently as well... can we standardize?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sydney-runkle