Ë
    ¬;jÞ  ã                   ó\   —  G d „ de «      Z G d„ de«      Z G d„ de«      Z G d„ de«      Zy)	c                   ó   — e Zd Zy)Ú
_JediErrorN)Ú__name__Ú
__module__Ú__qualname__© ó    úd/workspace/moltex-experiments/.pixi/envs/default/lib/python3.12/site-packages/jedi/api/exceptions.pyr   r      s   „ Ør   r   c                   ó   — e Zd ZdZy)Ú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y)Ú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y)Ú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      s5   ðô	�ô 	ô�Jô ô�:ô ô
�zõ 
r   