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 terry.reedy
Recipients Claudiu.Popa, ezio.melotti, fwierzbicki, jeff.allen, orsenthil, python-dev, r.david.murray, terry.reedy
Date 2014-10-17.16:04:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413561897.19.0.127480595945.issue20155@psf.upfronthosting.co.za>
In-reply-to
Content
If Python itself works correctly on a machine, it is a bug for a test to say that is it not, by failing.  Should we change
-        response = self.request('/', method='get')
to
+        response = self.request('/', method='gets')
or
+        response = self.request('/', method='custom')

or conditionally, on type(status), change the test from assertEqual to (after substitutions) assertIn(response.status, (200,501))? David, do you have a preference?  or should I flip a coin?
History
Date User Action Args
2014-10-17 16:04:57terry.reedysetrecipients: + terry.reedy, orsenthil, fwierzbicki, ezio.melotti, r.david.murray, Claudiu.Popa, python-dev, jeff.allen
2014-10-17 16:04:57terry.reedysetmessageid: <1413561897.19.0.127480595945.issue20155@psf.upfronthosting.co.za>
2014-10-17 16:04:57terry.reedylinkissue20155 messages
2014-10-17 16:04:57terry.reedycreate