o ÑtPf· ã@s2dZddlZddlmZdgZGdd„deƒZdS)z( Native thread-based hostname resolver. éN)Úget_hubÚResolverc@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@|durtƒ}|j|_tj|jvr|jtjtjf7_dSdS©N)rÚ threadpoolÚpoolÚ_socketÚgaierrorÚ NOT_ERRORÚherror)ÚselfÚhub©r úW/var/www/html/humari/django-venv/lib/python3.10/site-packages/gevent/resolver/thread.pyÚ__init__$s  ýzResolver.__init__cCs"dt|ƒjt|ƒjt|ƒ|jfS)Nz<%s.%s at 0x%x pool=%r>)ÚtypeÚ __module__Ú__name__Úidr©r r r rÚ__repr__-s  þzResolver.__repr__cCsdSrr rr r rÚclose2szResolver.closecGó|j tj|¡Sr)rÚapplyrÚ gethostbyname©r Úargsr r rr8ózResolver.gethostbynamecGrr)rrrÚgethostbyname_exrr r rr;rzResolver.gethostbyname_excOó|j tj||¡Sr)rrrÚ getaddrinfo©r rÚkwargsr r rr>ózResolver.getaddrinfocOrr)rrrÚ gethostbyaddrr r r rr#Ar"zResolver.gethostbyaddrcOrr)rrrÚ getnameinfor r r rr$Dr"zResolver.getnameinfor) rrÚ __qualname__Ú__doc__rrrrrrr#r$r r r rr s   )r&rÚ gevent.hubrÚ__all__Úobjectrr r r rÚs