archlinux关于neovim python module采用python-pynvim

[popjdh]

archwiki的neovim介绍中有提及python-pynvim, 在Prerequisites的介绍中是否可将原有的pip install neovim --user修改为pacman -S python-pynvim

[Jint-lzxy]

Yep but u should use this with caution. The following must be satisfied, otherwise Neovim may fail to find this provider (For most of the time this will not be an issue, but when you somehow mess up your environment, this will be a tough one to debug).

• This is the only python installed on your system. Parallel installation is usually not supported (unless you can guarantee this python will always be close to the front of ur $PATH, including non-interactive shells)
• ur python3, pip3 is a link to python, pip
• All other executables (e.g., pip, pip3) belong to this python package

Why not pip install neovim --user? Do you have any concerns?

[CharlesChiuGit]

Interesting post, I solve the issue myself in another method, which is installed as many things as possible at user level (or home dir).

For example:
https://github.com/CharlesChiuGit/dotfiles/tree/main/install_scripts

[popjdh]

@CharlesChiuGit It seems that you are installing and managing most of the dependencies through your own scripts (under the "app" and "update" folders).

For systems such as ubuntu, it may be good, but for systems like archLinux with rolling updates, it may be a bit troublesome. You need to add an additional pacman hook to synchronize updates in the system update.

[CharlesChiuGit]

no need lol
the script i wrote are mostly disentangled from the system pkgs. The initial idea of creating those scripts is b/c ubuntu updates it's repo too slow, sometimes i need the bleeding-edge releases directly from the github, installing those apps in user space is just a good side effect.

not to mention most apps i use is written in golang or rust, their toolchain is pretty self-sustaining; therefore disentangle themselves from system pkg even further and will work on most linux distros, macos and windows.

only some c-based apps, like tmux, need some libs from the system pkg, but their very few and i can manually deal with that.

[popjdh]

It sounds like a good design. On archLinux, you can try to build a PKGBUILD for direct maintenance using pacman.

[CharlesChiuGit]

u could do that, but it won't be cross-distro or cross-os.

[ayamir]

You are right. For archlinux, it's better to install python module by pacman. I have edited the wiki.

[popjdh]

I need to correct it, something like pip install neovim is still necessary.
For different Python project, users may use system level Python or Python in a virtual environment, so the "neovim" package needs to be installed in each environment.

• For system level Python, you need to use pacman -S python-pynvim.
• For virtual environment, you should use corresponding installation command. For example, installing this package under Conda should use conda install -c conda-forge neovim

Therefore, it may be necessary to point out that users need to choose the installation method based on the environment they are using, and provide some examples of mainstream environment(system python, pipx, conda, etc).

[CharlesChiuGit]

https://youtu.be/35PQrzG0rG4

Seems like it's not Arch's own problem.