➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, r.david.murray
Date 2014-02-01.22:08:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391292485.67.0.381493162498.issue20476@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2014-02-01 22:08:05r.david.murraysetrecipients: + r.david.murray, barry
2014-02-01 22:08:05r.david.murraysetmessageid: <1391292485.67.0.381493162498.issue20476@psf.upfronthosting.co.za>
2014-02-01 22:08:05r.david.murraylinkissue20476 messages
2014-02-01 22:08:05r.david.murraycreate