a
    Š©lcß  ã                   @   sD   G d d„ de ƒZG dd„ deƒZG dd„ deƒZG dd„ deƒZdS )	c                   @   s   e Zd ZdS )Ú
_JediErrorN)Ú__name__Ú
__module__Ú__qualname__© r   r   úO/var/www/html/django/DPS/env/lib/python3.9/site-packages/jedi/api/exceptions.pyr      s   r   c                   @   s   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   c                   @   s   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
   c                   @   s   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 ususally 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   N)Ú	Exceptionr   r   r
   r   r   r   r   r   Ú<module>   s   	