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 flox
Recipients flox, ned.deily, pitrou
Date 2012-07-08.08:45:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341737114.75.0.344524078651.issue15285@psf.upfronthosting.co.za>
In-reply-to
Content
Something like 127.42.42.42 might be more reliable, because it does not depend on the LAN configuration, only on the local loopback settings.
It is in 127.0.0.0/8 but not in 127.0.0.0/32.
Tested OK here.


127.0.0.0/8 - This block is assigned for use as the Internet host
   loopback address.  A datagram sent by a higher-level protocol to an
   address anywhere within this block loops back inside the host.  This
   is ordinarily implemented using only 127.0.0.1/32 for loopback.  As
   described in [RFC1122], Section 3.2.1.3, addresses within the entire
   127.0.0.0/8 block do not legitimately appear on any network anywhere.

http://tools.ietf.org/html/rfc5735#section-3
History
Date User Action Args
2012-07-08 08:45:14floxsetrecipients: + flox, pitrou, ned.deily
2012-07-08 08:45:14floxsetmessageid: <1341737114.75.0.344524078651.issue15285@psf.upfronthosting.co.za>
2012-07-08 08:45:14floxlinkissue15285 messages
2012-07-08 08:45:13floxcreate