Message236970
| Author |
demian.brecht |
| Recipients |
demian.brecht, jimr, martin.panter |
| Date |
2015年03月01日.17:30:10 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<B0E6F676-D230-4B91-9347-F9D46D95D19F@gmail.com> |
| In-reply-to |
<1425226029.41.0.646585210296.issue23539@psf.upfronthosting.co.za> |
| Content |
> but I wonder if that goes beyond the scope of this issue?
I think it’s worthwhile to fix it while you’re already working on the logic there. I’d consider Content-Type being set for methods not expecting it as a (very) minor bug and it’s better to clear up the inconsistent behaviour. That said, it /is/ breaking backwards compatibility (however slightly) and would likely need to get sign-off from a couple core devs. |
|