Closed petschki closed 1 month ago
when running the tests we've encountered the following error in testvalidateSingleEmailAddress
testvalidateSingleEmailAddress
AssertionError: True is not false : user@example.org Bcc: user@example.org should fail
this is because email.utils.getaddresses has changed its strategy to "strict parsing" in the newest Python 3.11 and 3.12 versions. (see https://docs.python.org/3.12/whatsnew/3.12.html#id11 and https://docs.python.org/3.11/whatsnew/3.11.html#email)
email.utils.getaddresses
add the parameter strict=False to get the old behavior back and test with getattr(email.utils, 'supports_strict_parsing', False) if this parameter is available
strict=False
getattr(email.utils, 'supports_strict_parsing', False)
new approach: respect the new output from strict parsing.
Fix got merged. Thanks!
mauritsvanrees
commented
1 month ago
when running the tests we've encountered the following error in
testvalidateSingleEmailAddressthis is because
email.utils.getaddresseshas changed its strategy to "strict parsing" in the newest Python 3.11 and 3.12 versions. (see https://docs.python.org/3.12/whatsnew/3.12.html#id11 and https://docs.python.org/3.11/whatsnew/3.11.html#email)proposed solution:
add the parameterstrict=Falseto get the old behavior back and test withgetattr(email.utils, 'supports_strict_parsing', False)if this parameter is availablenew approach: respect the new output from strict parsing.