]>
Commit | Line | Data |
---|---|---|
53e6db90 DC |
1 | class _JediError(Exception): |
2 | pass | |
3 | ||
4 | ||
5 | class InternalError(_JediError): | |
6 | """ | |
7 | This error might happen a subprocess is crashing. The reason for this is | |
8 | usually broken C code in third party libraries. This is not a very common | |
9 | thing and it is safe to use Jedi again. However using the same calls might | |
10 | result in the same error again. | |
11 | """ | |
12 | ||
13 | ||
14 | class WrongVersion(_JediError): | |
15 | """ | |
16 | This error is reserved for the future, shouldn't really be happening at the | |
17 | moment. | |
18 | """ | |
19 | ||
20 | ||
21 | class RefactoringError(_JediError): | |
22 | """ | |
23 | Refactorings can fail for various reasons. So if you work with refactorings | |
24 | like :meth:`.Script.rename`, :meth:`.Script.inline`, | |
25 | :meth:`.Script.extract_variable` and :meth:`.Script.extract_function`, make | |
26 | sure to catch these. The descriptions in the errors are usually valuable | |
27 | for end users. | |
28 | ||
29 | A typical ``RefactoringError`` would tell the user that inlining is not | |
30 | possible if no name is under the cursor. | |
31 | """ |