-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Remove default module globals from types namespace #10123
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
|
On this branch: On |
|
So this doesn't make a huge difference in terms of memory usage, but it makes debugging and namespace management cleaner / easier. |
CodSpeed Performance ReportMerging #10123 will not alter performanceComparing Summary
|
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
Deploying pydantic-docs with
|
| Latest commit: |
aa8b29d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6d56da38.pydantic-docs.pages.dev |
| Branch Preview URL: | https://ns-cluttering.pydantic-docs.pages.dev |
|
I've added |
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.
LGTM, though we should keep an eye out for anything this change might break, wouldn't surprise me if there were some exotic scenarios that might be affected, but it seems to me that worst case you will just need to manually rebuild, so I think it should be okay.
On `main` right now, when we store or fetch namespaces for classes, we get a mess as shown below
This takes up lots of unneeded space, and we don't use these global defaults for type resolution or schema building, so there's no reason for us to store them.
Makes progress on #10074