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 demian.brecht, jimr, martin.panter, orsenthil, r.david.murray
Date 2015-03-02.15:19:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425309547.34.0.459677590953.issue23539@psf.upfronthosting.co.za>
In-reply-to
Content
Don't break backward compatibility.  It's not like this was reported as a bug that caused a problem for real world code, it is about theoretical consistency.  The risk of breaking someone code is much higher than the benefit of any such consistency, when talking about a bug fix.

Aside from that, however, I see request.('GET', '/') and request.('GET', '/', '') as clearly *different* from an API call standpoint, so I would in any case preserve the existing behavior.
History
Date User Action Args
2015-03-02 15:19:07r.david.murraysetrecipients: + r.david.murray, orsenthil, martin.panter, demian.brecht, jimr
2015-03-02 15:19:07r.david.murraysetmessageid: <1425309547.34.0.459677590953.issue23539@psf.upfronthosting.co.za>
2015-03-02 15:19:07r.david.murraylinkissue23539 messages
2015-03-02 15:19:07r.david.murraycreate