Bug#729924: vim: Add Python 3 support

[Barry Warsaw]

On Jan 31, 2014, at 11:04 PM, James McCoy wrote:

>First, the way Debian builds Python prevents loading both libpython2 and
>libpython3 in the same process, since Debian's builds necessitate
>passing RTLD_GLOBAL to dlopen().  This means that when Vim is built to
>support both Python 2 & 3, one has to choose between using plugins that
>target Python 2 or Python 3 instead of the user being able to use both.

I'd always envisioned that the end user would make a binary choice as to
whether their plugins were Python 2 or 3, and then use one or the other in
their vim process.  I don't know whether that's a reasonable assumption
though.

I think we have other such precedence in Debian; I remember hacking on some
package to dynamically load either Python 2 or Python 3 (but not both) support
at runtime, but now I can't remember which package that is.  I personally
don't think you'd need to support *both* Python 2 and Python 3 in the same
process space, and I'm actually pretty skeptical that that would work!

Does it change anything in your mind if vim plugins were limited to either
Python 2 or Python 3, selectable at runtime by the end user?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20140203/f89738b4/attachment.sig>