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, drlazor8, jev2, r.david.murray
Date 2021-04-23.16:51:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1619196667.61.0.600141169116.issue43922@roundup.psfhosted.org>
In-reply-to
Content
Since python is doing the right thing here, I don't see a particularly good reason to put a hack into the stdlib to fix the failure of third party software to adhere to standards.  (On the output side.  We do follow Postel's rule on input and try hard to handle broken but recoverable input.)  I don't actually *object* to it, though, as long as it follows the standard on output, and is a *simple* change.

Please note that you can fix this locally by implementing and using a custom content manager.
History
Date User Action Args
2021-04-23 16:51:07r.david.murraysetrecipients: + r.david.murray, barry, drlazor8, jev2
2021-04-23 16:51:07r.david.murraysetmessageid: <1619196667.61.0.600141169116.issue43922@roundup.psfhosted.org>
2021-04-23 16:51:07r.david.murraylinkissue43922 messages
2021-04-23 16:51:07r.david.murraycreate