New submission from R. David Murray: This was part of the design of the new stuff added in 3.4, so it is a bug that it doesn't work...somehow I missed implementing this detail. The full implementation should make this a policy setting, so that a custom policy could specify its own factory. However, since 3.4 is in beta it would be a bad time to add that to the policy.
The patch proposed here implements the required behavior by hardcoding any non-compat32 policy to use EmailMessage instead of Message in feedparser. ---------- components: email files: use_emailmessage.patch keywords: patch messages: 209921 nosy: barry, r.david.murray priority: high severity: normal stage: commit review status: open title: If new email policies are used, default message factory should be EmailMessage type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file33848/use_emailmessage.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20476> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
