-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
New issue
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
If new email policies are used, default message factory should be EmailMessage #64675
Comments
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. |
New changeset 77082b818676 by R David Murray in branch 'default': |
I'm leaving this open and changing the version to 3.5 to remind myself to fix this right once default is open for 3.5 changes. |
Here's the patch to add the message_factory policy attribute. |
New changeset 9ba8f4be0651 by R David Murray in branch 'default': |
New changeset 8375b8d54bf7 by R David Murray in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: