Auto merge of #3176 - micbou:python-docs, r=bstaletic

[READY] Update docs about the default version of Python used for completion

The behavior of `get_default_environment` has been changed in the latest version of Jedi. Instead of picking the latest version of Python available on the system, it now uses the one it's running on i.e. the one running ycmd in our case. See https://github.com/davidhalter/jedi/issues/1196. Update the docs accordingly.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/valloric/youcompleteme/3176)
<!-- Reviewable:end -->
This commit is contained in:
zzbot 2018-10-08 08:48:47 -07:00 committed by GitHub
commit a98bc72668
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 7 deletions

View File

@ -1146,9 +1146,9 @@ present so we'd love to hear your feedback! Please do remember to check
### Python Semantic Completion ### Python Semantic Completion
YCM relies on the [Jedi][] engine to provide completion and code navigation. By YCM relies on the [Jedi][] engine to provide completion and code navigation. By
default, it will pick the latest version of Python available on your system and default, it will pick the version of Python running the [ycmd server][ycmd] and
use its default `sys.path`. While this is fine for simple projects, this needs use its `sys.path`. While this is fine for simple projects, this needs to be
to be configurable when working with virtual environments or in a project with configurable when working with virtual environments or in a project with
third-party packages. The next sections explain how to do that. third-party packages. The next sections explain how to do that.
#### Working with virtual environments #### Working with virtual environments

View File

@ -1375,10 +1375,10 @@ for the list of diagnostics we'll need.
Python Semantic Completion ~ Python Semantic Completion ~
YCM relies on the Jedi [12] engine to provide completion and code navigation. YCM relies on the Jedi [12] engine to provide completion and code navigation.
By default, it will pick the latest version of Python available on your system By default, it will pick the version of Python running the ycmd server [46] and
and use its default 'sys.path'. While this is fine for simple projects, this use its 'sys.path'. While this is fine for simple projects, this needs to be
needs to be configurable when working with virtual environments or in a project configurable when working with virtual environments or in a project with third-
with third-party packages. The next sections explain how to do that. party packages. The next sections explain how to do that.
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
*youcompleteme-working-with-virtual-environments* *youcompleteme-working-with-virtual-environments*