You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

365 lines
12 KiB

4 years ago
  1. ###################################################################
  2. Jedi - an awesome autocompletion/static analysis library for Python
  3. ###################################################################
  4. .. image:: https://img.shields.io/pypi/v/jedi.svg?style=flat
  5. :target: https://pypi.python.org/pypi/jedi
  6. :alt: PyPI version
  7. .. image:: https://img.shields.io/pypi/pyversions/jedi.svg
  8. :target: https://pypi.python.org/pypi/jedi
  9. :alt: Supported Python versions
  10. .. image:: https://travis-ci.org/davidhalter/jedi.svg?branch=master
  11. :target: https://travis-ci.org/davidhalter/jedi
  12. :alt: Linux Tests
  13. .. image:: https://ci.appveyor.com/api/projects/status/mgva3bbawyma1new/branch/master?svg=true
  14. :target: https://ci.appveyor.com/project/davidhalter/jedi/branch/master
  15. :alt: Windows Tests
  16. .. image:: https://coveralls.io/repos/davidhalter/jedi/badge.svg?branch=master
  17. :target: https://coveralls.io/r/davidhalter/jedi
  18. :alt: Coverage status
  19. *If you have specific questions, please add an issue or ask on* `Stack Overflow
  20. <https://stackoverflow.com/questions/tagged/python-jedi>`_ *with the label* ``python-jedi``.
  21. Jedi is a static analysis tool for Python that can be used in IDEs/editors. Its
  22. historic focus is autocompletion, but does static analysis for now as well.
  23. Jedi is fast and is very well tested. It understands Python on a deeper level
  24. than all other static analysis frameworks for Python.
  25. Jedi has support for two different goto functions. It's possible to search for
  26. related names and to list all names in a Python file and infer them. Jedi
  27. understands docstrings and you can use Jedi autocompletion in your REPL as
  28. well.
  29. Jedi uses a very simple API to connect with IDEs. There's a reference
  30. implementation as a `VIM-Plugin <https://github.com/davidhalter/jedi-vim>`_,
  31. which uses Jedi's autocompletion. We encourage you to use Jedi in your IDEs.
  32. It's really easy.
  33. Jedi can currently be used with the following editors/projects:
  34. - Vim (jedi-vim_, YouCompleteMe_, deoplete-jedi_, completor.vim_)
  35. - Emacs (Jedi.el_, company-mode_, elpy_, anaconda-mode_, ycmd_)
  36. - Sublime Text (SublimeJEDI_ [ST2 + ST3], anaconda_ [only ST3])
  37. - TextMate_ (Not sure if it's actually working)
  38. - Kate_ version 4.13+ supports it natively, you have to enable it, though. [`proof
  39. <https://projects.kde.org/projects/kde/applications/kate/repository/show?rev=KDE%2F4.13>`_]
  40. - Atom_ (autocomplete-python-jedi_)
  41. - `GNOME Builder`_ (with support for GObject Introspection)
  42. - `Visual Studio Code`_ (via `Python Extension <https://marketplace.visualstudio.com/items?itemName=ms-python.python>`_)
  43. - Gedit (gedi_)
  44. - wdb_ - Web Debugger
  45. - `Eric IDE`_ (Available as a plugin)
  46. - `IPython 6.0.0+ <https://ipython.readthedocs.io/en/stable/whatsnew/version6.html>`_
  47. and many more!
  48. Here are some pictures taken from jedi-vim_:
  49. .. image:: https://github.com/davidhalter/jedi/raw/master/docs/_screenshots/screenshot_complete.png
  50. Completion for almost anything (Ctrl+Space).
  51. .. image:: https://github.com/davidhalter/jedi/raw/master/docs/_screenshots/screenshot_function.png
  52. Display of function/class bodies, docstrings.
  53. .. image:: https://github.com/davidhalter/jedi/raw/master/docs/_screenshots/screenshot_pydoc.png
  54. Pydoc support (Shift+k).
  55. There is also support for goto and renaming.
  56. Get the latest version from `github <https://github.com/davidhalter/jedi>`_
  57. (master branch should always be kind of stable/working).
  58. Docs are available at `https://jedi.readthedocs.org/en/latest/
  59. <https://jedi.readthedocs.org/en/latest/>`_. Pull requests with documentation
  60. enhancements and/or fixes are awesome and most welcome. Jedi uses `semantic
  61. versioning <https://semver.org/>`_.
  62. If you want to stay up-to-date (News / RFCs), please subscribe to this `github
  63. thread <https://github.com/davidhalter/jedi/issues/1063>`_.:
  64. Installation
  65. ============
  66. pip install jedi
  67. Note: This just installs the Jedi library, not the editor plugins. For
  68. information about how to make it work with your editor, refer to the
  69. corresponding documentation.
  70. You don't want to use ``pip``? Please refer to the `manual
  71. <https://jedi.readthedocs.org/en/latest/docs/installation.html>`_.
  72. Feature Support and Caveats
  73. ===========================
  74. Jedi really understands your Python code. For a comprehensive list what Jedi
  75. understands, see: `Features
  76. <https://jedi.readthedocs.org/en/latest/docs/features.html>`_. A list of
  77. caveats can be found on the same page.
  78. You can run Jedi on CPython 2.7 or 3.4+ but it should also
  79. understand/parse code older than those versions. Additionally you should be able
  80. to use `Virtualenvs <https://jedi.readthedocs.org/en/latest/docs/api.html#environments>`_
  81. very well.
  82. Tips on how to use Jedi efficiently can be found `here
  83. <https://jedi.readthedocs.org/en/latest/docs/features.html#recipes>`_.
  84. API
  85. ---
  86. You can find the documentation for the `API here <https://jedi.readthedocs.org/en/latest/docs/api.html>`_.
  87. Autocompletion / Goto / Pydoc
  88. -----------------------------
  89. Please check the API for a good explanation. There are the following commands:
  90. - ``jedi.Script.goto_assignments``
  91. - ``jedi.Script.completions``
  92. - ``jedi.Script.usages``
  93. The returned objects are very powerful and really all you might need.
  94. Autocompletion in your REPL (IPython, etc.)
  95. -------------------------------------------
  96. Starting with IPython `6.0.0` Jedi is a dependency of IPython. Autocompletion
  97. in IPython is therefore possible without additional configuration.
  98. It's possible to have Jedi autocompletion in REPL modes - `example video <https://vimeo.com/122332037>`_.
  99. This means that in Python you can enable tab completion in a `REPL
  100. <https://jedi.readthedocs.org/en/latest/docs/usage.html#tab-completion-in-the-python-shell>`_.
  101. Static Analysis / Linter
  102. ------------------------
  103. To do all forms of static analysis, please try to use ``jedi.names``. It will
  104. return a list of names that you can use to infer types and so on.
  105. Linting is another thing that is going to be part of Jedi. For now you can try
  106. an alpha version ``python -m jedi linter``. The API might change though and
  107. it's still buggy. It's Jedi's goal to be smarter than classic linter and
  108. understand ``AttributeError`` and other code issues.
  109. Refactoring
  110. -----------
  111. Jedi's parser would support refactoring, but there's no API to use it right
  112. now. If you're interested in helping out here, let me know. With the latest
  113. parser changes, it should be very easy to actually make it work.
  114. Development
  115. ===========
  116. There's a pretty good and extensive `development documentation
  117. <https://jedi.readthedocs.org/en/latest/docs/development.html>`_.
  118. Testing
  119. =======
  120. The test suite depends on ``tox`` and ``pytest``::
  121. pip install tox pytest
  122. To run the tests for all supported Python versions::
  123. tox
  124. If you want to test only a specific Python version (e.g. Python 2.7), it's as
  125. easy as ::
  126. tox -e py27
  127. Tests are also run automatically on `Travis CI
  128. <https://travis-ci.org/davidhalter/jedi/>`_.
  129. For more detailed information visit the `testing documentation
  130. <https://jedi.readthedocs.org/en/latest/docs/testing.html>`_.
  131. Acknowledgements
  132. ================
  133. - Takafumi Arakaki (@tkf) for creating a solid test environment and a lot of
  134. other things.
  135. - Danilo Bargen (@dbrgn) for general housekeeping and being a good friend :).
  136. - Guido van Rossum (@gvanrossum) for creating the parser generator pgen2
  137. (originally used in lib2to3).
  138. .. _jedi-vim: https://github.com/davidhalter/jedi-vim
  139. .. _youcompleteme: https://valloric.github.io/YouCompleteMe/
  140. .. _deoplete-jedi: https://github.com/zchee/deoplete-jedi
  141. .. _completor.vim: https://github.com/maralla/completor.vim
  142. .. _Jedi.el: https://github.com/tkf/emacs-jedi
  143. .. _company-mode: https://github.com/syohex/emacs-company-jedi
  144. .. _elpy: https://github.com/jorgenschaefer/elpy
  145. .. _anaconda-mode: https://github.com/proofit404/anaconda-mode
  146. .. _ycmd: https://github.com/abingham/emacs-ycmd
  147. .. _sublimejedi: https://github.com/srusskih/SublimeJEDI
  148. .. _anaconda: https://github.com/DamnWidget/anaconda
  149. .. _wdb: https://github.com/Kozea/wdb
  150. .. _TextMate: https://github.com/lawrenceakka/python-jedi.tmbundle
  151. .. _Kate: https://kate-editor.org
  152. .. _Atom: https://atom.io/
  153. .. _autocomplete-python-jedi: https://atom.io/packages/autocomplete-python-jedi
  154. .. _GNOME Builder: https://wiki.gnome.org/Apps/Builder
  155. .. _Visual Studio Code: https://code.visualstudio.com/
  156. .. _gedi: https://github.com/isamert/gedi
  157. .. _Eric IDE: https://eric-ide.python-projects.org
  158. .. :changelog:
  159. Changelog
  160. ---------
  161. 0.13.1 (2018-10-02)
  162. +++++++++++++++++++
  163. - Bugfixes, because tensorflow completions were still slow.
  164. 0.13.0 (2018-10-02)
  165. +++++++++++++++++++
  166. - A small release. Some bug fixes.
  167. - Remove Python 3.3 support. Python 3.3 support has been dropped by the Python
  168. foundation.
  169. - Default environments are now using the same Python version as the Python
  170. process. In 0.12.x, we used to load the latest Python version on the system.
  171. - Added ``include_builtins`` as a parameter to usages.
  172. - ``goto_assignments`` has a new ``follow_builtin_imports`` parameter that
  173. changes the previous behavior slightly.
  174. 0.12.1 (2018-06-30)
  175. +++++++++++++++++++
  176. - This release forces you to upgrade parso. If you don't, nothing will work
  177. anymore. Otherwise changes should be limited to bug fixes. Unfortunately Jedi
  178. still uses a few internals of parso that make it hard to keep compatibility
  179. over multiple releases. Parso >=0.3.0 is going to be needed.
  180. 0.12.0 (2018-04-15)
  181. +++++++++++++++++++
  182. - Virtualenv/Environment support
  183. - F-String Completion/Goto Support
  184. - Cannot crash with segfaults anymore
  185. - Cleaned up import logic
  186. - Understand async/await and autocomplete it (including async generators)
  187. - Better namespace completions
  188. - Passing tests for Windows (including CI for Windows)
  189. - Remove Python 2.6 support
  190. 0.11.1 (2017-12-14)
  191. +++++++++++++++++++
  192. - Parso update - the caching layer was broken
  193. - Better usages - a lot of internal code was ripped out and improved.
  194. 0.11.0 (2017-09-20)
  195. +++++++++++++++++++
  196. - Split Jedi's parser into a separate project called ``parso``.
  197. - Avoiding side effects in REPL completion.
  198. - Numpy docstring support should be much better.
  199. - Moved the `settings.*recursion*` away, they are no longer usable.
  200. 0.10.2 (2017-04-05)
  201. +++++++++++++++++++
  202. - Python Packaging sucks. Some files were not included in 0.10.1.
  203. 0.10.1 (2017-04-05)
  204. +++++++++++++++++++
  205. - Fixed a few very annoying bugs.
  206. - Prepared the parser to be factored out of Jedi.
  207. 0.10.0 (2017-02-03)
  208. +++++++++++++++++++
  209. - Actual semantic completions for the complete Python syntax.
  210. - Basic type inference for ``yield from`` PEP 380.
  211. - PEP 484 support (most of the important features of it). Thanks Claude! (@reinhrst)
  212. - Added ``get_line_code`` to ``Definition`` and ``Completion`` objects.
  213. - Completely rewritten the type inference engine.
  214. - A new and better parser for (fast) parsing diffs of Python code.
  215. 0.9.0 (2015-04-10)
  216. ++++++++++++++++++
  217. - The import logic has been rewritten to look more like Python's. There is now
  218. an ``Evaluator.modules`` import cache, which resembles ``sys.modules``.
  219. - Integrated the parser of 2to3. This will make refactoring possible. It will
  220. also be possible to check for error messages (like compiling an AST would give)
  221. in the future.
  222. - With the new parser, the evaluation also completely changed. It's now simpler
  223. and more readable.
  224. - Completely rewritten REPL completion.
  225. - Added ``jedi.names``, a command to do static analysis. Thanks to that
  226. sourcegraph guys for sponsoring this!
  227. - Alpha version of the linter.
  228. 0.8.1 (2014-07-23)
  229. +++++++++++++++++++
  230. - Bugfix release, the last release forgot to include files that improve
  231. autocompletion for builtin libraries. Fixed.
  232. 0.8.0 (2014-05-05)
  233. +++++++++++++++++++
  234. - Memory Consumption for compiled modules (e.g. builtins, sys) has been reduced
  235. drastically. Loading times are down as well (it takes basically as long as an
  236. import).
  237. - REPL completion is starting to become usable.
  238. - Various small API changes. Generally this release focuses on stability and
  239. refactoring of internal APIs.
  240. - Introducing operator precedence, which makes calculating correct Array
  241. indices and ``__getattr__`` strings possible.
  242. 0.7.0 (2013-08-09)
  243. ++++++++++++++++++
  244. - Switched from LGPL to MIT license.
  245. - Added an Interpreter class to the API to make autocompletion in REPL
  246. possible.
  247. - Added autocompletion support for namespace packages.
  248. - Add sith.py, a new random testing method.
  249. 0.6.0 (2013-05-14)
  250. ++++++++++++++++++
  251. - Much faster parser with builtin part caching.
  252. - A test suite, thanks @tkf.
  253. 0.5 versions (2012)
  254. +++++++++++++++++++
  255. - Initial development.