We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
check_deliverability=False
See
pydantic/pydantic/networks.py
Line 742 in 07b6473
While we're at it, it would be nice to normalize as well.
.model_dump()
.model_dump_json()
model_construct()
The text was updated successfully, but these errors were encountered:
Generally we try to discourage doing networking within validation, mostly because there's no way to do async in a validator.
async
Sorry, something went wrong.
That's a good point.
How about normalization?
@tamird,
Seems reasonable re normalization, but I think it makes sense to move this feature request to email-validator. Closing as not planned here for now!
email-validator
email-validator already does normalization. it is not possible to use it though with EmailStr.
EmailStr
No branches or pull requests
Initial Checks
Description
See
pydantic/pydantic/networks.py
Line 742 in 07b6473
While we're at it, it would be nice to normalize as well.
Affected Components
.model_dump()
and.model_dump_json()
model_construct()
, pickling, private attributes, ORM modeThe text was updated successfully, but these errors were encountered: