
    Mh                     v     G d  de           Z G d de          Z G d de          Z G d de          ZdS )	c                       e Zd ZdS )
_JediErrorN)__name__
__module____qualname__     S/var/www/html/test/jupyter/venv/lib/python3.11/site-packages/jedi/api/exceptions.pyr   r      s        Dr   r   c                       e Zd ZdZdS )InternalErrora  
    This error might happen a subprocess is crashing. The reason for this is
    usually broken C code in third party libraries. This is not a very common
    thing and it is safe to use Jedi again. However using the same calls might
    result in the same error again.
    Nr   r   r   __doc__r   r   r	   r   r      s           r   r   c                       e Zd ZdZdS )WrongVersionza
    This error is reserved for the future, shouldn't really be happening at the
    moment.
    Nr   r   r   r	   r   r      s           r   r   c                       e Zd ZdZdS )RefactoringErrora  
    Refactorings can fail for various reasons. So if you work with refactorings
    like :meth:`.Script.rename`, :meth:`.Script.inline`,
    :meth:`.Script.extract_variable` and :meth:`.Script.extract_function`, make
    sure to catch these. The descriptions in the errors are usually valuable
    for end users.

    A typical ``RefactoringError`` would tell the user that inlining is not
    possible if no name is under the cursor.
    Nr   r   r   r	   r   r      s        	 	 	 	r   r   N)	Exceptionr   r   r   r   r   r   r	   <module>r      s   	 	 	 	 	 	 	 	    J       :   
 
 
 
 
z 
 
 
 
 
r   