B ÐH/\½ ã@s<dZddlZddlmZdgZd d¡Gdd„deƒZdS)z( Native thread-based hostname resolver. éN)Úget_hubÚResolverZfooZidnac@sReZdZdZddd„Zdd„Zdd„Zd d „Zd d „Zd d„Z dd„Z dd„Z dS)ra¹ Implementation of the resolver API using native threads and native resolution functions. Using the native resolution mechanisms ensures the highest compatibility with what a non-gevent program would return including good support for platform specific configuration mechanisms. The use of native (non-greenlet) threads ensures that a caller doesn't block other greenlets. This implementation also has the benefit of being very simple in comparison to :class:`gevent.resolver_ares.Resolver`. .. tip:: Most users find this resolver to be quite reliable in a properly monkey-patched environment. However, there have been some reports of long delays, slow performance or even hangs, particularly in long-lived programs that make many, many DNS requests. If you suspect that may be happening to you, try the dnspython or ares resolver (and submit a bug report). NcCs<|dkrtƒ}|j|_tj|jkr8|jtjtjf7_dS)N)rZ threadpoolÚpoolÚ_socketZgaierrorZ NOT_ERRORZherror)ÚselfZhub©rú5lib/python3.7/site-packages/gevent/resolver/thread.pyÚ__init__(s  zResolver.__init__cCsdt|ƒ|jfS)Nz1)Úidr)rrrrÚ__repr__1szResolver.__repr__cCsdS)Nr)rrrrÚclose4szResolver.closecGs|j tj|¡S)N)rÚapplyrÚ gethostbyname)rÚargsrrrr:szResolver.gethostbynamecGs|j tj|¡S)N)rr rÚgethostbyname_ex)rrrrrr=szResolver.gethostbyname_excOs|j tj||¡S)N)rr rÚ getaddrinfo)rrÚkwargsrrrr@szResolver.getaddrinfocOs|j tj||¡S)N)rr rÚ gethostbyaddr)rrrrrrrCszResolver.gethostbyaddrcOs|j tj||¡S)N)rr rÚ getnameinfo)rrrrrrrFszResolver.getnameinfo)N) Ú__name__Ú __module__Ú __qualname__Ú__doc__r r r rrrrrrrrrrs )rrZ gevent.hubrÚ__all__ÚencodeÚobjectrrrrrÚs