VimPlug/jedi-fork
1
0
Fork 0
forked from VimPlug/jedi
Code Pull Requests Activity

Installation notes for docs moved down in priority a bit

Browse Source
This commit is contained in:
Dave Halter
2020-03-15 23:52:52 +01:00
parent 0f25eb9c9a
commit 43363936cd
2 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/installation.rst
+9
View File
@@ -3,6 +3,15 @@
Installation and Configuration Installation and Configuration
============================== ==============================
.. warning:: Most people will want to install Jedi as a submodule/vendored and
not through pip/system wide. The reason for this is that it makes sense that
the plugin that uses Jedi has always access to it. Otherwise Jedi will not
work properly when virtualenvs are activated. So please read the
documentation of your editor/IDE plugin to install Jedi.
For plugin developers, Jedi works best if it is always available. Vendoring
is a pretty good option for that.
You can either include |jedi| as a submodule in your text editor plugin (like You can either include |jedi| as a submodule in your text editor plugin (like
jedi-vim_ does by default), or you can install it systemwide. jedi-vim_ does by default), or you can install it systemwide.
docs/index.rst
+1 -1
View File
@@ -21,10 +21,10 @@ Docs
:maxdepth: 2 :maxdepth: 2
docs/usage docs/usage
docs/installation
docs/features docs/features
docs/api docs/api
docs/api-classes docs/api-classes
docs/installation
docs/settings docs/settings
docs/development docs/development
docs/testing docs/testing