Steve P added the comment: I saw that issue, or one like it. I was very tempted to not report but the README says if there are any test failures, there is a problem. (I suppose it could mean there is a problem with my ISP, not python.) The dilemma is that we want to be able to count on a clean pass of all tests even in the face of the misbehaving ISP (I believe someone in the discussion said there may be more of such in the future).
At the very least, if we are accepting a failure in the test suite as "ok", the README should say something to that effect. On 10/14/2014 09:32 PM, Ned Deily wrote: > Ned Deily added the comment: > > Thanks for the additional information. It appears this is a duplicate of > Issue17564 with the root cause being the ISP not properly rejecting an > undefined host name as expected by the test case. See the discussion there > for more information. > > ---------- > resolution: -> duplicate > stage: -> resolved > status: open -> closed > superseder: -> test_urllib2_localnet fails > type: crash -> > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue22639> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22639> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
