python/cpython#46 or bpo-29463added docstring as a property to the module class that comes out ofAST (so the free strings no longer appear an the first element in theparsed files).

python/cpython#46 or bpo-29463added docstring as a property to the module class that comes out ofAST (so the free strings no longer appear an the first element in theparsed files).

python/cpython#46 /https://bugs.python.org/issue29463 move the module comment into theAST node and hence out of the tree which means the 2nd entry in thetree is now the import rather than the `__version__` string.Adds nightly on travis.

* FIX: install on python 3.7python/cpython#46 /https://bugs.python.org/issue29463 move the module comment into theAST node and hence out of the tree which means the 2nd entry in thetree is now the import rather than the `__version__` string.Adds nightly on travis.* BLD: update python tags in setup.py* CI: switch to 3.7-dev* CI: allow failure on 3.7 dev

* Pin pytest to latest version 3.3.2* Pin pytest-asyncio to latest version 0.8.0* Pin pytest-aiohttp to latest version 0.3.0* Update cherry_picker from 0.2.5 to 0.2.7* Pin aiohttp to latest version 2.3.9* Pin gidgethub to latest version 2.4.1* Pin cachetools to latest version 2.0.1* Pin requests to latest version 2.18.4* Pin redis to latest version 2.10.6* Pin celery to latest version 4.1.0* Comment out python 3.7 from travis CI

Bump version numberClosespython#46

Update pyproject.toml and setup.pyClosespython#46See merge request python-devs/importlib_resources!47

…sprinttest: Fix fstring related tests in test_tokenize.py

Co-authored-by: Ken Jin <kenjin4096@gmail.com>

Email generators had been incorrectly flattening non-ASCII emailaddresses to RFC 2047 encoded-word format, leaving them undeliverable.(RFC 2047 prohibits use of encoded-word in an addr-spec.)This change raises a ValueError when attempting to flatten anEmailMessage with a non-ASCII addr-spec and a policy with utf8=False.(Exception: If the non-ASCII address originated from parsing a message,it will be flattened as originally parsed, without error.)Non-ASCII email addresses are supported when using a policy withutf8=True (such as email.policy.SMTPUTF8) under RFCs 6531 and 6532.Non-ASCII email address domains (but not localparts) can also be usedwith non-SMTPUTF8 policies by encoding the domain as an IDNA A-label.(The email package does not perform this encoding, because it cannotknow whether the caller wants IDNA 2003, IDNA 2008, or some othervariant such as UTSpython#46.)

Email generators had been incorrectly flattening non-ASCII emailaddresses to RFC 2047 encoded-word format, leaving them undeliverable.(RFC 2047 prohibits use of encoded-word in an addr-spec.)This change raises a ValueError when attempting to flatten anEmailMessage with a non-ASCII addr-spec and a policy with utf8=False.(Exception: If the non-ASCII address originated from parsing a message,it will be flattened as originally parsed, without error.)Non-ASCII email addresses are supported when using a policy withutf8=True (such as email.policy.SMTPUTF8) under RFCs 6531 and 6532.Non-ASCII email address domains (but not localparts) can also be usedwith non-SMTPUTF8 policies by encoding the domain as an IDNA A-label.(The email package does not perform this encoding, because it cannotknow whether the caller wants IDNA 2003, IDNA 2008, or some othervariant such as UTSpython#46.)

Email generators had been incorrectly flattening non-ASCII emailaddresses to RFC 2047 encoded-word format, leaving them undeliverable.(RFC 2047 prohibits use of encoded-word in an addr-spec.)This change raises a ValueError when attempting to flatten anEmailMessage with a non-ASCII addr-spec and a policy with utf8=False.(Exception: If the non-ASCII address originated from parsing a message,it will be flattened as originally parsed, without error.)Non-ASCII email addresses are supported when using a policy withutf8=True (such as email.policy.SMTPUTF8) under RFCs 6531 and 6532.Non-ASCII email address domains (but not localparts) can also be usedwith non-SMTPUTF8 policies by encoding the domain as an IDNA A-label.(The email package does not perform this encoding, because it cannotknow whether the caller wants IDNA 2003, IDNA 2008, or some othervariant such as UTSpython#46.)

Email generators had been incorrectly flattening non-ASCII emailaddresses to RFC 2047 encoded-word format, leaving them undeliverable.(RFC 2047 prohibits use of encoded-word in an addr-spec.)This change raises a ValueError when attempting to flatten anEmailMessage with a non-ASCII addr-spec and a policy with utf8=False.(Exception: If the non-ASCII address originated from parsing a message,it will be flattened as originally parsed, without error.)Non-ASCII email addresses are supported when using a policy withutf8=True (such as email.policy.SMTPUTF8) under RFCs 6531 and 6532.Non-ASCII email address domains (but not localparts) can also be usedwith non-SMTPUTF8 policies by encoding the domain as an IDNA A-label.(The email package does not perform this encoding, because it cannotknow whether the caller wants IDNA 2003, IDNA 2008, or some othervariant such as UTSpython#46.)

Email generators had been incorrectly flattening non-ASCII emailaddresses to RFC 2047 encoded-word format, leaving them undeliverable.(RFC 2047 prohibits use of encoded-word in an addr-spec.)This change raises a ValueError when attempting to flatten anEmailMessage with a non-ASCII addr-spec and a policy with utf8=False.(Exception: If the non-ASCII address originated from parsing a message,it will be flattened as originally parsed, without error.)Non-ASCII email addresses are supported when using a policy withutf8=True (such as email.policy.SMTPUTF8) under RFCs 6531 and 6532.Non-ASCII email address domains (but not localparts) can also be usedwith non-SMTPUTF8 policies by encoding the domain as an IDNA A-label.(The email package does not perform this encoding, because it cannotknow whether the caller wants IDNA 2003, IDNA 2008, or some othervariant such as UTSpython#46.)