a lct;@sdZddlZddlZddlmZmZddlmZddlmZm Z m Z ddl m Z m Z ddlmZddlmZdd lmZmZmZdd lmZdd lmZGd d d eZeZe GdddeZGdddZGdddeZdddddZ dS)z An embedded IPython shell. N)ultratb compilerop)magic_arguments)Magics magics_class line_magic)DummyModInteractiveShell)TerminalInteractiveShell)load_default_config)BoolCBoolUnicode) ask_yes_no)Setc@s eZdZdS) KillEmbeddedN)__name__ __module__ __qualname__rrR/var/www/html/django/DPS/env/lib/python3.9/site-packages/IPython/terminal/embed.pyrrc @sfeZdZeeejdddddejdddddejd d dd ddd dZedddZdS)EmbeddedMagicsz-iz --instance store_truez&Kill instance instead of call location)actionhelpz-xz--exitzAlso exit the current sessionz-yz--yeszDo not ask confirmationcCst|j|}t||jrJ|js.tdd}nd}|rt|jtdn*|js\tdd}nd}|rtd|j_ td|j r|j dS) a#%kill_embedded : deactivate for good the current embedded IPython This function (after asking for confirmation) sets an internal flag so that an embedded IPython will never activate again for the given call location. This is useful to permanently disable a shell that is being called inside a loop: once you've figured out what you needed from it, you may then kill it and the program will then continue to run without the interactive shell interfering again. Kill Instance Option: If for some reasons you need to kill the location where the instance is created and not called, for example if you create a single instance in one place and debug in many locations, you can use the ``--instance`` option to kill this specific instance. Like for the ``call location`` killing an "instance" should work even if it is recreated within a loop. .. note:: This was the default behavior before IPython 5.2 zc Ksd|_|dd}|s2td} d| jj| jf}||_|jsBdSd|_ |sZ|dkr^|j r^dS|r|j |_ |j d|d|_ nd |_ |j r||j||||d |j |_ |jdurt|j|jrtd dS) aActivate the interactive interpreter. __call__(self,header='',local_ns=None,module=None,dummy=None) -> Start the interpreter shell with the given local and global namespaces, and optionally print a header string at startup. The shell can be globally activated/deactivated using the dummy_mode attribute. This allows you to turn off a shell used for debugging globally. However, *each* time you call the shell you can override the current state of dummy_mode with the optional keyword parameter 'dummy'. For example, if you set dummy mode on with IPShell.dummy_mode = True, you can still have a specific call work by making it as IPShell(dummy=False). Tr;Nr>r?Fr r) stack_depth compile_flagsz2Embedded IPython raising error, as user requested.)Z keep_runningrCrDrErFrGrHr;r$Zexit_now dummy_modeZbanner2Z old_banner2display_bannerZ show_bannermainloopexit_msgrr+r) r'headerlocal_nsmoduledummyrVrWrNrOrPrrr__call__s2    zInteractiveShellEmbed.__call__rc s|dus|dus|durjrt|j}|dur8|j}|dur|j}ztj|d}Wn4tyt d| ddt }||_ Yn0|dur|j jtj@}j}j}jj} |dur|_|durfdd|D} | _|dur|j_j@jWdn1s:0YWdn1sZ0Y|dur|fddjD|_|_| j_dS)aEmbeds IPython into a running python program. Parameters ---------- local_ns, module Working local namespace (a dict) and module (a module or similar object). If given as None, they are automatically taken from the scope where the shell was called, so that program variables become visible. stack_depth : int How many levels in the stack to go to looking for namespaces (when local_ns or module is None). This allows an intermediate caller to make sure that this function gets the namespace from the intended level in the stack. By default (0) it will get its locals and globals from the immediate caller. compile_flags A bit field identifying the __future__ features that are enabled, as passed to the builtin :func:`compile` function. If given as None, they are automatically taken from the scope where the shell was called. NrzFailed to get module %szunknown modulecs$i|]\}}|jvr||qSrZuser_ns_hiddenkeys.0kvr4rr Drz2InteractiveShellEmbed.mainloop..cs$i|]\}}|jvr||qSrrarcr4rrrgUr)Zdefault_user_namespacesrDrEf_backf_locals f_globalsmodulesKeyErrorwarningswarngetr__dict__rFco_flagsrZ PyCF_MASKZ user_moduleZuser_nscompileflagsitemsZ init_user_nsZset_completer_frameZ builtin_trap display_trapinteractupdate) r'r]r^rVrW call_frame global_nsZorig_user_moduleZ orig_user_nsZorig_compile_flagsZreentrant_local_nsrr4rrZsN     H zInteractiveShellEmbed.mainloop)rNNNr>N)NNrN)rrrr rXrr[r Zembeddedr+rYtagZ term_titlesetr8rr1__annotations__r#propertyr$setterr3rSrTr`rZ __classcell__rrrQrr6ws@     Ir6r)r\rWc Ks<|d}|dur(t}|j|_||d<|dd}|rV|dd|d|dkdid}d}ztj}tj}WntyYn0t j }|durt |}| t d} tjfd d | jj| jfi|} | |d |d | jj| jfd t |dur"t |}| |D] } || _ q|dur8|t_|t_dS) aCall this to embed IPython at the current point in your program. The first invocation of this will create an :class:`InteractiveShellEmbed` instance and then call it. Consecutive calls just call the already created instance. If you don't want the kernel to initialize the namespace from the scope of the surrounding function, and/or you want to load full IPython configuration, you probably want `IPython.start_ipython()` instead. Here is a simple example:: from IPython import embed a = 10 b = 20 embed(header='First time') c = 30 d = 40 embed() Full customization can be done by passing a :class:`Config` in as the config argument. r7Nusingsyncr NoColor)Z loop_runnerrKZ autoawaitr>r:r?)r\rVrWr;)ror r r6rwrDps1ps2AttributeErrorr _instancetypeclear_instancerEr rFrGrH _walk_mro) r\rWkwargsr7rrrZsaved_shell_instanceclsrPr"subclassrrrembed^sJ           r)!__doc__rDrm IPython.corerrrZIPython.core.magicrrrIPython.core.interactiveshellrr !IPython.terminal.interactiveshellr IPython.terminal.ipappr traitletsr r rZIPython.utils.iortypingr ExceptionrZ KillEmbededrr.r6rrrrrs&     N h