On Sun, Jul 17, 2011 at 12:12 AM, Maciej Fijalkowski <fij...@gmail.com> wrote:
> On Thu, Jul 7, 2011 at 7:59 PM, Oleg Broytman <p...@phdru.name> wrote:
>> Hello.
>>
>>   We are sorry but we cannot help you. This mailing list is to work on
>> developing Python (adding new features to Python itself and fixing bugs);
>
> Well, it seems this post is about adding a new feature isn't it?

Not really - the key question was "How can I get python to correctly
use cached dns lookups and ipv4 only (at least in those cases where it
is appropriate)." This isn't the place to ask that question
(particularly since it's the wrong question - the real question is why
the IPv6 lookups are taking so long. Since we just call into the C
standard library for name resolution, whether it's slow or fast is an
OS configuration problem).

The latter part (very indirectly) made a feature suggestion via the
reference off to the SO question. However, hardcoding the *app* to be
IPv4 only really isn't a good workaround for IPv6 resolution taking a
long time to fail at the OS level. Exposing those flags would
encourage people to do exactly that, and that would be a *really* bad
idea (it's unfortunate enough that PEP 3144 stalled, or we might have
had better support for manipulating IPv6 addresses in the standard
library by now. We really shouldn't make things even worse by making
it easy for developers with broken IPv6 setups to switch off IPv6
support entirely).

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to