-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Fix ImportString special cases
#10137
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.
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
Conversation
Deploying pydantic-docs with
|
| Latest commit: |
3c5e4a0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://49125506.pydantic-docs.pages.dev |
| Branch Preview URL: | https://test-import-string.pydantic-docs.pages.dev |
CodSpeed Performance ReportMerging #10137 will not alter performanceComparing Summary
|
| # Handle special cases for sys.XXX streams | ||
| # if we see more of these, we should consider a more general solution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in general serializing the imported object to a string is a hard (even impossible without special casing as it is done here) problem, so I'm fine with the proposed solution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks!
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
Fix #10122
I can understand the argument for a more general solution, but I wasn't able to find an easy workaround for io wrappers. Feedback welcome!