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 jaraco
Recipients cstratak, gregory.p.smith, jaraco, larry, martin.panter, miss-islington, orange, rschiron, serhiy.storchaka, vstinner, ware, xiang.zhang, xtreak
Date 2019-09-14.20:38:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This change caused a regression or two captured in issue36274. Essentially, by blocking invalid requests, it's now not possible for a system intentionally to generate invalid requests for testing purposes. As these point releases of Python start making it into the wild, the impact of this change will likely increase.

I think this patch was applied at too low a level. That is, instead of protecting the user inputs, the change protects the programmer's inputs.

I mention this here so those interested can follow the mitigation work happening in issue36274.
Date User Action Args
2019-09-14 20:38:54jaracosetrecipients: + jaraco, gregory.p.smith, vstinner, larry, martin.panter, serhiy.storchaka, xiang.zhang, cstratak, orange, miss-islington, xtreak, ware, rschiron
2019-09-14 20:38:54jaracosetmessageid: <>
2019-09-14 20:38:54jaracolinkissue30458 messages
2019-09-14 20:38:53jaracocreate