➜

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 andrei.avk, grant.b.edwards, r.david.murray
Date 2021-11-24.01:46:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1637718418.48.0.37331828137.issue45299@roundup.psfhosted.org>
In-reply-to
Content 
In this case the docs are correct and the code has a bug.  The intent was that if the message passed in to BytesGenerator has a policy, that policy should be followed.  If it is not being followed, that's a bug in BytesGenerator.  The tricky part of course is backward compatibility.  Is there code out there depending on this bug?  Anyone want to hazard a guess?

Are there things other than mangle_from_ that are being ignored? 

If we decide it is too risky to fix in BytesGenerator (or maybe only to fix it in a feature release), then I'd pass the whole policy in the else clause, with a comment about what bug it is working around.
History
Date User Action Args
2021-11-24 01:46:58r.david.murraysetrecipients: + r.david.murray, andrei.avk, grant.b.edwards
2021-11-24 01:46:58r.david.murraysetmessageid: <1637718418.48.0.37331828137.issue45299@roundup.psfhosted.org>
2021-11-24 01:46:58r.david.murraylinkissue45299 messages
2021-11-24 01:46:58r.david.murraycreate