ó
    Ð]jÞ  ã                   ó\   •  " S  S\ 5      r " S S\5      r " S S\5      r " S S\5      rg)	c                   ó   • \ rS rSrSrg)Ú
_JediErroré   © N)Ú__name__Ú
__module__Ú__qualname__Ú__firstlineno__Ú__static_attributes__r   ó    ÚP/home/mande/repo/quber/.venv/lib/python3.13/site-packages/jedi/api/exceptions.pyr   r      s   † Úr   r   c                   ó   • \ rS rSrSrSrg)ÚInternalErroré   zÿ
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.
r   N©r   r   r   r	   Ú__doc__r
   r   r   r   r   r      s   † ôr   r   c                   ó   • \ rS rSrSrSrg)ÚWrongVersioné   zU
This error is reserved for the future, shouldn't really be happening at the
moment.
r   Nr   r   r   r   r   r      s   † ôr   r   c                   ó   • \ rS rSrSrSrg)ÚRefactoringErroré   a˜  
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.
r   Nr   r   r   r   r   r      s   † ô	r   r   N)Ú	Exceptionr   r   r   r   r   r   r   Ú<module>r      s5   ðô	�ô 	ô�Jô ô�:ô ô
�zõ 
r   