- This module provides a single method, valid_email_address(), which returns
True or False to indicate whether a given address is valid according to the ‘addr-spec’ part of the specification given in [RFC 2822] (http://www.ietf.org/rfc/rfc2822.txt). Ideally, we would like to find this in some other library, already thoroughly tested and well- maintained. The standard Python library email.utils contains a parse_addr() function, but it is not sufficient to detect many malformed addresses.
This implementation aims to be faithful to the RFC, with the exception of a circular definition (see comments inline), and with the omission of the pattern components marked as “obsolete”.
Yes, all this really does is build a big regular expression. But it builds it in nice pieces that correspond to the RFC, and there’s a big bunch of unit tests that try to ensure each little piece of the regexp works as intended. (See test_email_validation.py.)
Metadata
Release files for py_email_validation 1.0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| py_email_validation-1.0.0.3.tar.gz | 2.6 kB | Details |
Release files / py_email_validation-1.0.0.3.tar.gz
| Download URL | py_email_validation-1.0.0.3.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1efd83a901f5cd2dfd918525a3b604ab4b13dbc3435659bc039fae500226365b
|
|
BLAKE2b-256 checksum How to use checksums |
08962091f030a6482dbf7c0bba2c3f88a1accf6733fdfc709914cd269dcc9ea9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |