Bug 1450624 - Set default python_host_prog for neovim
Summary: Set default python_host_prog for neovim
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: neovim
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-14 03:11 UTC by Elliott Sales de Andrade
Modified: 2018-06-20 14:47 UTC (History)
2 users (show)

Fixed In Version: neovim-0.3.0-1.fc28
Clone Of:
Environment:
Last Closed: 2018-06-20 14:47:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Elliott Sales de Andrade 2017-05-14 03:11:23 UTC
Description of problem:
The neovim package currently Recommends python2-neovim and python3-neovim. It would be nice if neovim had some global setting of:

let g:python_host_prog = '/usr/bin/python2'
let g:python3_host_prog = '/usr/bin/python3'

The reason why is that if you have a virtualenv or conda env, neovim will pick the first interpreter on the path, which is not Fedora's copy. Then it will say that the Python neovim package isn't available. Setting both of these globals will cause neovim to skip the search and use the right interpreter directly.


Version-Release number of selected component (if applicable):
neovim-0.2.0-1.fc25.x86_64
python2-neovim-0.1.13-1.fc25.noarch
python3-neovim-0.1.13-1.fc25.noarch


Steps to Reproduce:
1. Install neovim.
2. Enable a virtualenv or conda env.
3. Run :CheckHealth in neovim

Actual results:
## Python 3 provider (optional)
  - WARNING: No Python interpreter was found with the neovim module.  Using the first available for diagnostics.
  - WARNING: provider/pythonx: Could not load Python 3:
    conda-env/bin/python3 does not have the "neovim" module. :help provider-python
    python3.7 not found in search path or not executable.
    python3.6 not found in search path or not executable.
    conda-env/bin/python3.5 does not have the "neovim" module. :help provider-python
    python3.3 not found in search path or not executable.
    conda-env/bin/python does not have the "neovim" module. :help provider-python
  - ERROR: Python provider error
    - SUGGESTIONS:
      - provider/pythonx: Could not load Python 3:
          conda-env/bin/python3 does not have the "neovim" module. :help provider-python
          python3.7 not found in search path or not executable.
          python3.6 not found in search path or not executable.
          conda-env/bin/python3.5 does not have the "neovim" module. :help provider-python
          python3.3 not found in search path or not executable.
          conda-env/bin/python does not have the "neovim" module. :help provider-python
  - INFO: Executable: Not found


Expected results:
## Python 3 provider (optional)
  - INFO: Using: g:python3_host_prog = "/usr/bin/python3"
  - INFO: Executable: /usr/bin/python3
  - INFO: Python3 version: 3.5.3
  - INFO: python3-neovim version: 0.1.13
  - SUCCESS: Latest python3-neovim is installed: 0.1.13

Comment 1 Filip Szymański 2017-05-15 14:10:57 UTC
The Python providers could be placed in the `sysinit.vim` file I a added some time ago.

Comment 2 Elliott Sales de Andrade 2017-11-08 09:22:49 UTC
Just a ping as a reminder that a new neovim release is out and it would be nice to get this fixed with it.

Comment 3 Fedora End Of Life 2017-11-16 18:47:11 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Elliott Sales de Andrade 2017-11-16 19:12:18 UTC
It seems like it checks for 3.6 now, but still the same problem exists.

Comment 5 Fedora End Of Life 2018-05-03 08:26:02 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Elliott Sales de Andrade 2018-05-03 22:55:07 UTC
I don't see anything changing in the sysinit.vim; CheckHealth still fails as in the original description.

Comment 7 Andreas Schneider 2018-05-04 11:35:14 UTC
Could you please provide a patch?

Comment 8 Fedora Update System 2018-06-11 09:04:15 UTC
neovim-0.3.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8a8a9839c8

Comment 9 Fedora Update System 2018-06-11 16:32:40 UTC
neovim-0.3.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8a8a9839c8

Comment 10 Fedora Update System 2018-06-20 14:47:03 UTC
neovim-0.3.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.