-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[READY] Search user defined python binary also in PATH #429
Conversation
Could you summarize the difference between this and #424 for those of us without the full context? Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion. ycmd/utils.py, line 190 [r1] (raw file): Comments from the review on Reviewable.io |
Actually this is basically what we've discussed with @allangarret on #424, but I was already experimenting with this approach and I thought that instead than trying out, explaining to him what to do and check I just opened a PR myself. Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion. Comments from the review on Reviewable.io |
95af122
to
1888839
Compare
Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion. ycmd/utils.py, line 190 [r1] (raw file): Comments from the review on Reviewable.io |
I understand that this PR is a result of a prior discussion, but that's spread out, involves reading the code in the other PR etc. Writing a couple of sentences in this PR describing the intent makes things clearer both for current reviewers and people reaching this PR by going through git history. Reviewed 3 of 3 files at r2. ycmd/utils.py, line 39 [r2] (raw file): Comments from the review on Reviewable.io |
As of right now is possible to specify which Python interpreter to use when spawning a JediHTTP instance by setting the
To achieve this I've adapted out The only doubt that I still have is if we want to check that what is passed is really a Python interpreter, similar to what YCM does before spawning Review status: all files reviewed at latest revision, 1 unresolved discussion. Comments from the review on Reviewable.io |
Thanks for the clarification. I think this approach is good. I don't think we need to check is it a Python interpreter; we do that in YCM because I'm on this, though I would like to see some tests for this. It will require quite a bit of mocking though. Review status: all files reviewed at latest revision, 2 unresolved discussions. ycmd/utils.py, line 191 [r2] (raw file): Comments from the review on Reviewable.io |
I tested it in a virtualenv on Windows and it was working so with minor comments. Reviewed 3 of 3 files at r2. ycmd/utils.py, line 39 [r2] (raw file): ycmd/utils.py, line 188 [r2] (raw file): Comments from the review on Reviewable.io |
I tested on archlinux using virtualenvs for python2 and python3 and the autocompletion works out of the box with third party packages with I think we should add a note inside YouCompleteMe documentation about this setting and virtualenv usage, because it will solve, at least, issues 587 and 609. Please, feel free to close #424 and merge this instead, so on this Review status: all files reviewed at latest revision, 3 unresolved discussions. Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 3 unresolved discussions, all commit checks successful. ycmd/utils.py, line 191 [r2] (raw file): Comments from the review on Reviewable.io |
Once I finish to write the tests and this gets merged in I will send a PR on YCM for updating the docs 👍 Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful. Comments from the review on Reviewable.io |
What's the state of this PR now? |
I actually forgot about this (shame on me 😭 ). I was on a short vacation, so I'll resume this work ASAP. |
No need for the ASAP part; take your time. :) |
1888839
to
0898d34
Compare
I've updated the jedi_completer tests and added a couple one for |
97f6361
to
90d0ad3
Compare
Reviewed 4 of 4 files at r3. ycmd/utils.py, line 223 [r4] (raw file):
There is still a blank line here. Not important though. ycmd/utils.py, line 246 [r4] (raw file):
Comments from Reviewable |
90d0ad3
to
b7ab0d2
Compare
Review status: 4 of 5 files reviewed at latest revision, 3 unresolved discussions. ycmd/utils.py, line 223 [r4] (raw file):
|
Anything else to do here? the coverage decreased because more Windows code was added and coveralls counts only the linux build (maybe would be actually helpful to look at codecov.io... I guess I'll do that this weekend) |
Tests are not passing on Windows. |
363bae7
to
d9ce74d
Compare
No I didn't saw it, but I guess that I'm close enough to at least see if I can make it work 😝 |
521492f
to
abb7e3e
Compare
cccfd83
to
275b13b
Compare
275b13b
to
cef8799
Compare
Now I think I got it. In the end I made what @micbou already did, but oh well 😝 For the coverage drop I'm looking at codecov, since the coverage went down because more windows-only code was needed for windows 😒 |
Do you want to wait for codecov to merge this PR?
|
It would actually be nice to have codecov right away but since it simplify the use of Jedi for virtualenv I'm not sure 😕 What do you think?
|
cef8799
to
4268395
Compare
Let's merge this. Adding coverage for Windows is less important. @homu r+
|
📌 Commit 4268395 has been approved by |
[READY] Search user defined python binary also in PATH I'm marking as an RFC because there is also #424 which does almost the same thing. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Review on Reviewable"/>](https://reviewable.io/reviews/valloric/ycmd/429) <!-- Reviewable:end -->
☀️ Test successful - status |
We need to document this feature in YCM README. |
[RFC] Document find first executable for ycm_python_binary_path # PR Prelude Thank you for working on YCM! :) **Please complete these steps and check these boxes (by putting an `x` inside the brackets) _before_ filing your PR:** - [x] I have read and understood YCM's [CONTRIBUTING][cont] document. - [x] I have read and understood YCM's [CODE_OF_CONDUCT][code] document. - [x] I have included tests for the changes in my PR. If not, I have included a rationale for why I haven't. - [x] **I understand my PR may be closed if it becomes obvious I didn't actually perform all of these steps.** # Why this change is necessary and useful This will document the enhancement that ycm-core/ycmd#429 brought to YCM. When this will be ready I will update the vim documentation too. [Please explain **in detail** why the changes in this PR are needed.] [cont]: https://github.com/Valloric/YouCompleteMe/blob/master/CONTRIBUTING.md [code]: https://github.com/Valloric/YouCompleteMe/blob/master/CODE_OF_CONDUCT.md <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/valloric/youcompleteme/2205) <!-- Reviewable:end -->
I'm marking as an RFC because there is also #424 which does almost the same thing.
This change is