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.

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

Handle Any type properly in pydantic type checking. Fixes #468 #471

Merged
merged 1 commit into from
Mar 4, 2025

Conversation

ptomecek
Copy link
Collaborator

@ptomecek ptomecek commented Mar 4, 2025

Fixes #468.
Also improve error messages when incorrectly using generic type (improves error messages for #469).

@ptomecek ptomecek added the lang: python Issues and PRs related to the Python codebase label Mar 4, 2025
@ptomecek ptomecek force-pushed the pit/handle_any_type branch from dc2ec85 to bc59be6 Compare March 4, 2025 16:37
robambalu
robambalu previously approved these changes Mar 4, 2025
…ssages when incorrectly using generic type.

Signed-off-by: Pascal Tomecek <pascal.tomecek@cubistsystematic.com>
@ptomecek
Copy link
Collaborator Author

ptomecek commented Mar 4, 2025

Keep trying to fix the typing.Any handling across all platforms...

@robambalu robambalu self-requested a review March 4, 2025 19:06
@ptomecek ptomecek merged commit 40c0f4d into main Mar 4, 2025
24 of 27 checks passed
@ptomecek ptomecek deleted the pit/handle_any_type branch March 4, 2025 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lang: python Issues and PRs related to the Python codebase
Projects
None yet
Development

Successfully merging this pull request may close these issues.

typing.Any fails as input annotation with Delayed edge
2 participants