o oi @s2dZddlZddlmZdgZGdddeZdS)z( Native thread-based hostname resolver. N)get_hubResolverc@sReZdZdZdddZddZddZd d Zd d Zd dZ ddZ ddZ 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_dSdSN)r threadpoolpool_socketgaierror NOT_ERRORherror)selfhubr U/var/www/html/pca-backend/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__idrr r r r__repr__-s  zResolver.__repr__cCsdSrr rr r rclose2szResolver.closecG|jtj|Sr)rapplyr gethostbynamer argsr r rr8zResolver.gethostbynamecGrr)rrrgethostbyname_exrr r rr;rzResolver.gethostbyname_excO|jtj||Sr)rrr getaddrinfor rkwargsr 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 rs