Bug#881633: Creation of vim-python3 virtual package
Thanks for starting the discussion, Victor.
One thing I'd like to note is that none of the vim-$lang virtual
packages are currently listed in Policy's set of virtual packages. That
was an oversight on the Vim maintainers side when the package names were
introduced, but maybe now would be a good time to correct that.
On Mon, Nov 13, 2017 at 09:04:55PM +0100, Víctor Cuadrado Juan wrote:
> On Mon, 13 Nov 2017 19:34:44 +0100 Víctor Cuadrado Juan <me@viccuad.me> wrot
> > It will allow vim python3 plugins to require on it.
>
> Expanding on the rationale:
>
> vim works with python2 and python3 plugins simultaneously.
Neovim does, Vim does not. Due to the way Python is built on Debian,
it's not possible for Vim's current language binding support to use both
languages in the same Vim instance.
When I switched the Vim packages from Python 2 to Python 3, I didn't
change the virtual package name. This was purely due to Vim's
limitations and not considering that Neovim could handle it better.
> Those vim python
> plugins depend on the vim-python virtual package.
>
> In the case of neovim, support for python2 and python3 plugins is achieved
> by using python-neovim and python3-neovim respectively.
>
> As the maintainer of python-neovim, if I would do only `Provides: vim-python`
> then some vim python plugins would be broken.
> Eg: vim-python-jedi, a python3 package, depends on vim-python. vim-python-jedi
> would not work with python-neovim that `Provides: vim-python`, buy would need
> python3-neovim that `Provides: vim-python3`
>
> This means that packages that currently depend on vim-python need to be checked
> to depend on the correct vim-python and/or vim-python3.
This sounds good to me, and I'll adapt Vim to Provide vim-python3
instead of vim-python.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Reply to: