➜

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 martin.panter
Recipients Garfield222, Lukasa, Pierre.Tardy, adambrenecki, berker.peksag, christian.heimes, demian.brecht, icordasc, jitterman, lonetwin, martin.panter, orsenthil, pitrou, r.david.murray, raymondr, serhiy.storchaka, stamparm
Date 2015-09-04.10:55:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441364159.21.0.136126518654.issue17849@psf.upfronthosting.co.za>
In-reply-to
Content 
Patch 3 looks better IMO. Now instead of the TypeError, we should see an error something like

socket.error: Tunnel connection failed: 200

I’ll commit this in a day or so, perhaps with an improved error message, like “Invalid response from tunnel request”.
History
Date User Action Args
2015-09-04 10:55:59martin.pantersetrecipients: + martin.panter, orsenthil, pitrou, christian.heimes, r.david.murray, berker.peksag, serhiy.storchaka, stamparm, icordasc, demian.brecht, adambrenecki, raymondr, Lukasa, lonetwin, Pierre.Tardy, jitterman, Garfield222
2015-09-04 10:55:59martin.pantersetmessageid: <1441364159.21.0.136126518654.issue17849@psf.upfronthosting.co.za>
2015-09-04 10:55:59martin.panterlinkissue17849 messages
2015-09-04 10:55:59martin.pantercreate