o Tj2@sUdZddlZddlZddlZddlZddlZddlZddlZddlZddl m Z ddl m Z ddlm Z mZmZmZmZedZGdddeZeeefZeZed ed <dd d ZeeGdd d ZGdddejZdS)aEnsure asyncio selector methods (add_reader, etc.) are available tornado 6.1 adds AddThreadSelectorEventLoop event loop, running select in a thread and defining these methods on the running event loop. This factors out the functionality of AddThreadSelectorEventLoop into a standalone SelectorThread object which can be attached to any running event loop. Vendored from tornado v6.4.0 Redistributed under license Apache-2.0 N)Callable)suppress)AnyOptionalProtocolTypeVarUnion_Tc@seZdZdefddZdS) _HasFilenoreturncCsdS)Nrselfr r ^/home/dinkstrade/pdmp-scanner/venv/lib/python3.10/site-packages/curl_cffi/_asyncio_selector.pyfileno sz_HasFileno.filenoN)__name__ __module__ __qualname__intrr r r rr sr SelectorThread_selector_loopsr c CstD]A}|jd|_|jWdn1swYtt|jdWdn1s4wY|jdurC|j qt dS)NTa) r _select_cond_closing_selectornotifyrBlockingIOError_waker_wsend_threadjoinclear)loopr r r_atexit_callback+s     r"c@s eZdZdZdZdejddfddZd(dd Zde j d fd d Z d(d dZ d(ddZ d(ddZd(ddZdeedeeddfddZdedeeefddfddZdededdeddfd d!Zdededdeddfd"d#Zdedefd$d%Zdedefd&d'ZdS))raqDefine ``add_reader`` methods to be called in a background select thread. Instances of this class start a second thread to run a selector. This thread is completely hidden from the user; all callbacks are run on the wrapped event loop's thread. Typically used via ``AddThreadSelectorEventLoop``, but can be attached to a running asyncio loop. F real_loopr Ncs|_t_d_d_d__dfdd j fddi_ i_ t \__jdjdtjjdS)NFr csjIdHdSN)_thread_manager_handle __anext__r r r rthread_manager_anextVsz5SelectorThread.__init__..thread_manager_anextcsjSr$) _real_loop create_taskr rr'r r_sz)SelectorThread.__init__..r N)r( threading Conditionr _select_argsrr_thread_managerr% call_soon_readers_writerssocket socketpair_waker_rr setblockingradd add_reader_consume_wakerrr#r r*r__init__Ks$      zSelectorThread.__init__cCs|jrdS|jd|_|jWdn1swY||jdur.|jt|| |j |j |j d|_dS)NT) _closedrrr_wake_selectorrrrdiscard remove_readerr6closerr r r rrAms        zSelectorThread.close)NNcCsNtjdd|jd|_|j|zdVWdSty&|w)NzTornado selectorT)namedaemontarget)r-Thread _run_selectrstart _start_select GeneratorExitrAr r r rr0|s   zSelectorThread._thread_managercCsD|jrdStt|jdWddS1swYdS)Nr)r=rrrrr r r rr>s  "zSelectorThread._wake_selectorcCs:tt|jdWddS1swYdS)Ni)rrr6recvr r r rr:s "zSelectorThread._consume_wakercCsb|j$|jdus Jt|jt|jf|_|jWddS1s*wYdSr$)rr/listr2keysr3rr r r rrHs  "zSelectorThread._start_selectc CsJ |j8|jdur|js|j|jdur|jr |jr& WddS|jdus-J|j\}}d|_Wdn1s?wYzt|||\}}}||}Wn2ty}z&|jttdtjkr{t|j gggd\}}}|rzg}nWYd}~nd}~wwz |j |j ||WntyYn tyYnwq)NT WSAENOTSOCKr)rr/rwaitselectOSErrorerrnogetattrEBADFr6rr(call_soon_threadsafe_handle_select RuntimeErrorAttributeError)rto_readto_writerswsxse_r r rrFsB       zSelectorThread._run_selectrZr[cCs<|D] }|||jq|D] }|||jq|dSr$) _handle_eventr2r3rH)rrZr[rwr r rrUs  zSelectorThread._handle_selectfdcb_mapcCs,z||}Wn tyYdSw|dSr$)KeyError)rrbrccallbackr r rr_s    zSelectorThread._handle_eventre.NargscG$tj|g|R|j|<|dSr$) functoolspartialr2r>rrbrergr r rr9 zSelectorThread.add_readercGrhr$)rirjr3r>rkr r r add_writerrlzSelectorThread.add_writercC.z|j|=Wn tyYdSw|dSNFT)r2rdr>rrbr r rr@  zSelectorThread.remove_readercCrnro)r3rdr>rpr r r remove_writerrqzSelectorThread.remove_writerr,)rrr__doc__r=asyncioAbstractEventLoopr<rAtypingAsyncGeneratorr0r>r:rHrFrK_FileDescriptorLikerUdictrr_rr9rmboolr@rrr r r rr>sX  "    @       cseZdZdZhdZdedeffdd Zdej ddfd d Z dd d Z d dde ddeddfddZ d dde ddeddfddZd ddefddZd ddefddZZS)AddThreadSelectorEventLoopaWrap an event loop to add implementations of the ``add_reader`` method family. Instances of this class start a second thread to run a selector. This thread is completely hidden from the user; all callbacks are run on the wrapped event loop's thread. This class is used automatically by Tornado; applications should not need to refer to it directly. It is safe to wrap any event loop with this class, although it only makes sense for event loops that do not implement the ``add_reader`` family of methods themselves (i.e. ``WindowsProactorEventLoop``) Closing the ``AddThreadSelectorEventLoop`` also closes the wrapped event loop. >rA _selectorr(r9rmr@rrrBr cs"|tjvr t|St|j|Sr$)r{ MY_ATTRIBUTESsuper__getattribute__rRr()rrB __class__r rr7s   z+AddThreadSelectorEventLoop.__getattribute__r#NcCs||_t||_dSr$)r(rr|r;r r rr<<sz#AddThreadSelectorEventLoop.__init__cCs|j|jdSr$)r|rAr(r r r rrA@s z AddThreadSelectorEventLoop.closerbrxrerfrgcG|jj||g|RSr$)r|r9rkr r rr9Dz%AddThreadSelectorEventLoop.add_readercGrr$)r|rmrkr r rrmLrz%AddThreadSelectorEventLoop.add_writercC |j|Sr$)r|r@rpr r rr@T z(AddThreadSelectorEventLoop.remove_readercCrr$)r|rrrpr r rrrWrz(AddThreadSelectorEventLoop.remove_writerr,)rrrrsr}strrrrtrur<rArr9rmrzr@rr __classcell__r r rrr{s4    r{r,)rsrtatexitrQrirOr4r-rvcollections.abcr contextlibrrrrrrr r rrxsetr__annotations__r"registerrrur{r r r rs*      \