forked from VimPlug/jedi
c28b337278
There are small typos in: - jedi/api/exceptions.py - jedi/inference/base_value.py - jedi/inference/compiled/mixed.py - jedi/inference/value/dynamic_arrays.py Fixes: - Should read `usually` rather than `ususally`. - Should read `modifications` rather than `modfications`. - Should read `interpreters` rather than `interpreteters`. - Should read `inferred` rather than `inferrined`. - Should read `completable` rather than `completeable`. Signed-off-by: Tim Gates <tim.gates@iress.com>
32 lines
990 B
Python
32 lines
990 B
Python
class _JediError(Exception):
|
|
pass
|
|
|
|
|
|
class InternalError(_JediError):
|
|
"""
|
|
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.
|
|
"""
|
|
|
|
|
|
class WrongVersion(_JediError):
|
|
"""
|
|
This error is reserved for the future, shouldn't really be happening at the
|
|
moment.
|
|
"""
|
|
|
|
|
|
class RefactoringError(_JediError):
|
|
"""
|
|
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.
|
|
"""
|