^h>SrSSKrSSKrSSKrSSKJr SSKrSr\S5r "SS\R5r "SS \ 5r \S 5r\S 5r\S 5rS r\"\R&S5r\S:a\rg\R,S:Xa\rg\rg!\a N'f=f)z;Enable wxPython to be used interactively in prompt_toolkit N) default_timerc^U4SjnU$)a/Decorator which causes KeyboardInterrupt exceptions to be ignored during execution of the decorated function. This is used by the inputhook functions to handle the event where the user presses CTRL+C while IPython is idle, and the inputhook loop is running. In this case, we want to ignore interrupts. c8>T"U0UD6 g![a gf=fN)KeyboardInterrupt)argskwargsfuncs [/home/james-whalen/.local/lib/python3.13/site-packages/IPython/terminal/pt_inputhooks/wx.pywrapper*ignore_keyboardinterrupts..wrappers'  $ !& !    s  )r r s` r ignore_keyboardinterruptsr s Nc\[R"5nUb[R"5(de[R"5n[R"U5nUR 5(a'UR 5 UR 5(aM'UR5 Ag)zRun the wx event loop by processing pending events only. This approach seems to work, but its performance is not great as it relies on having PyOS_InputHook called regularly. r)wxGetApp Thread_IsMain EventLoopEventLoopActivatorPendingDispatch ProcessIdle)contextappevtloopeas r inputhook_wx1rs~ ))+C !!!! ,,.  " "7 +oo    oo   rc \rSrSrSrSrSrg)EventLoopTimer2cNXl[RRU5 gr)r rTimer__init__)selfr s r r$EventLoopTimer.__init__4s  $rc$UR5 grr r%s r NotifyEventLoopTimer.Notify8s  rr(N)__name__ __module__ __qualname____firstlineno__r$r*__static_attributes__rrr r r 2s  rr c \rSrSrSrSrSrg)EventLoopRunner<cX l[R"5Ul[ UR 5UlUR RU5 URR5 gr) input_is_readyrrrr check_stdintimerStartRun)r%timer5s r r9EventLoopRunner.Run>sI,||~ #D$4$45   rcUR5(a5URR5 URR 5 ggr)r5r7StoprExitr)s r r6EventLoopRunner.check_stdinEs4    JJOO  LL    !r)rr5r7N)r,r-r.r/r9r6r0rrr r2r2<s  rr2c[R"5nUb@[R"5(de[5nUR SUR S9 g)a`Run the wx event loop, polling for stdin. This version runs the wx eventloop for an undetermined amount of time, during which it periodically checks to see if anything is ready on stdin. If anything is ready on stdin, the event loop exits. The argument to elr.Run controls how often the event loop looks at stdin. This determines the responsiveness at the keyboard. A setting of 1000 enables a user to type at most 1 char per second. I have found that a setting of 10 gives good keyboard response. We can shorten it further, but eventually performance would suffer from calling select/kbhit too often. )r:r5r)rrrr2r9r5)rrelrs r inputhook_wx2rCKsR ))+C !!!! R&55  7 rcb[R"5nUGb[R"5(de[[R "[R 55(d3[R"[R [R5 [R"5n[R"U5n[5nUR5(dUR5(a1[5nUR5 UR5(aM1UR5 [5U- nUS:a[R "S5 O3US:a[R "S5 O[R "S5 UR5(dMAg)aJRun the wx event loop by processing pending events only. This is like inputhook_wx1, but it keeps processing pending events until stdin is ready. After processing all pending events, a call to time.sleep is inserted. This is needed, otherwise, CPU usage is at 100%. This sleep time should be tuned though for best performance. g$@g?g?g?gMbP?r)rrrcallablesignal getsignalSIGINTdefault_int_handlerrrclockr5rrrr:sleep)rrrrt used_times r inputhook_wx3rNes% ))+C !!!! ((788 MM&--)C)C D,,.  " "7 + G((**//##G  "//## OO ! I4 3S 4  5!3((**4  rcL^^^[R"5mTcgTR5(ag[R"5(deSn[R"5mUUU4SjnTR U5 TR [RU5 [[R"[R55(d3[R"[R[R5 TRS5 TR5 g)adRun the wx event loop until the user provides more input. This input hook is suitable for use with wxPython >= 4 (a.k.a. Phoenix). It uses the same approach to that used in ipykernel.eventloops.loop_wx. The wx.MainLoop is executed, and a wx.Timer is used to periodically poll the context for input. As soon as input is ready, the wx.MainLoop is stopped. Ndcr>TR5(a!TR5 TR5 ggr)r5r= ExitMainLoop)evrrr7s r poll!inputhook_wxphoenix..polls,  ! ! # # JJL     $rF)rrr5 IsMainThreadr#r8Bind EVT_TIMERrErFrGrHrISetExitOnFrameDeleteMainLoop)r poll_intervalrTrr7s` @@r inputhook_wxphoenixr\s ))+C { ??   M HHJE  KK  JJr||T" F$$V]]3 4 4 fmmV%?%?@U#LLNrdarwin)__doc__sysrFr:timeitrrJrrrr#r objectr2rCrNr\ major_versionint __version__ Exception inputhookplatformrrr rjs )     ,RXX  f    20 0 f--b  q)*M A#I \\XII  sBBB