forked from VimPlug/jedi
docs: fix some incorrect reference and improve wording
This commit is contained in:
@@ -18,7 +18,7 @@ from . import fake
|
||||
|
||||
|
||||
class CheckAttribute(object):
|
||||
"""Raises an AttributeError if the attribute X isn't available."""
|
||||
"""Raises :exc:`AttributeError` if the attribute X is not available."""
|
||||
def __init__(self, func):
|
||||
self.func = func
|
||||
# Remove the py in front of e.g. py__call__.
|
||||
|
||||
@@ -171,7 +171,7 @@ class ModuleContext(TreeContext):
|
||||
|
||||
In case of a package, this returns Python's __path__ attribute, which
|
||||
is a list of paths (strings).
|
||||
Raises an AttributeError if the module is not a package.
|
||||
Raises :exc:`AttributeError` if the module is not a package.
|
||||
"""
|
||||
path = self._get_init_directory()
|
||||
|
||||
|
||||
@@ -3,8 +3,8 @@ Recursions are the recipe of |jedi| to conquer Python code. However, someone
|
||||
must stop recursions going mad. Some settings are here to make |jedi| stop at
|
||||
the right time. You can read more about them :ref:`here <settings-recursion>`.
|
||||
|
||||
Next to :mod:`jedi.evaluate.cache` this module also makes |jedi| not
|
||||
thread-safe. Why? ``execution_recursion_decorator`` uses class variables to
|
||||
Next to the internal ``jedi.evaluate.cache`` this module also makes |jedi| not
|
||||
thread-safe, because ``execution_recursion_decorator`` uses class variables to
|
||||
count the function calls.
|
||||
|
||||
.. _settings-recursion:
|
||||
@@ -34,7 +34,7 @@ from jedi.evaluate.base_context import NO_CONTEXTS
|
||||
|
||||
recursion_limit = 15
|
||||
"""
|
||||
Like ``sys.getrecursionlimit()``, just for |jedi|.
|
||||
Like :func:`sys.getrecursionlimit()`, just for |jedi|.
|
||||
"""
|
||||
total_function_execution_limit = 200
|
||||
"""
|
||||
|
||||
Reference in New Issue
Block a user