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 ned.deily
Recipients Roman.Rader, ned.deily
Date 2015-05-11.22:41:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431384076.61.0.622445731557.issue24156@psf.upfronthosting.co.za>
In-reply-to
Content
There are places in the test suite that assume 127.0.0.1 is the standard loopback address and will fail if the system under test doesn't follow that convention; see, for example, the discussion in Issue22753.  I suspect that, in your case, the system's host configuration (/etc/hosts, DNS configuration, or similar) is such that the loopback address (127.0.0.1) is "round-tripped" as the actual address (192.168.1.103) of the interface.  What platform are you running this on?  Can you check what the addresses association with "localhost" and the names associated with the two IP addresses?  For example, on many POSIX-y platforms, the following might work:

dig localhost
dig -x 127.0.0.1
dig -x 192.168.1.103
ifconfig
History
Date User Action Args
2015-05-11 22:41:16ned.deilysetrecipients: + ned.deily, Roman.Rader
2015-05-11 22:41:16ned.deilysetmessageid: <1431384076.61.0.622445731557.issue24156@psf.upfronthosting.co.za>
2015-05-11 22:41:16ned.deilylinkissue24156 messages
2015-05-11 22:41:16ned.deilycreate