On Fri, 31 Jan 2014 23:04:21 -0500 James McCoy wrote:
> At the time, this meant I had to choose one and I went with Python 2 due
> to the much higher prevalence of plugins targeting it. While Python 3
> has gained a lot of ground since then and it's much more easy to write
> code that works in bo
Just for the note, I've stumbled upon this bug report, and thought it
might be useful to tell that as I'm running wheezy and I needed a more
recent version of vim, I recompiled it and enabled both python3 and
python2:
8<8<8<---8<
VIM - Vi
On Mon, Feb 03, 2014 at 07:31:40PM -0500, James McCoy wrote:
> On Mon, Feb 03, 2014 at 05:38:12PM -0500, Barry Warsaw wrote:
> > 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
On Mon, Feb 03, 2014 at 05:38:12PM -0500, Barry Warsaw wrote:
> 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(). T
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
On Mon, Nov 18, 2013 at 05:59:02PM -0500, Barry Warsaw wrote:
> I'm not a vim user but I'm am very interested in porting the world to
> Python 3. To that end, I see that the current version of upstream vim
> supports Python 3, but building that is not currently enabled in the
> Debian package.
Th
Package: vim
Version: 2:7.4.052-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
I'm not a vim user but I'm am very interested in porting the world to
Python 3. To that end, I see that the current version of upstream vim
supports Python 3, but building that
7 matches
Mail list logo
