Debian Bug report logs - #729924
vim: Add Python 3 support

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: vim: Add Python 3 support

Date: Mon, 18 Nov 2013 17:59:02 -0500

[Message part 1 (text/plain, inline)]

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 is not currently enabled in the
Debian package.  With the attached patch, I am able to build a vim
that appears to support both Python 2 and Python 3 dynamically.  I
haven't actually tested it in real vim session since I don't really
know how that works. ;)  I'll try to enlist other vim/python users to
review.

- -- Package-specific info:

- --- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.basic
/usr/bin/vim is /usr/bin/vim.basic

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim depends on:
ii  libacl1      2.2.52-1
ii  libc6        2.17-96
ii  libgpm2      1.20.4-6.1
ii  libselinux1  2.2.1-1
ii  libtinfo5    5.9+20130608-1
ii  vim-common   2:7.4.052-1
ii  vim-runtime  2:7.4.052-1

vim recommends no packages.

Versions of packages vim suggests:
pn  ctags        <none>
pn  vim-doc      <none>
pn  vim-scripts  <none>

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJSipuzAAoJEBJutWOnSwa/TPkP/iuTwcjLZBG6QmcRKf2BeQTp
xc+uRXhm2xUPMwMyE29OTGyPUKZFUNJtK3/93qAICMFVqsaAlpXBPOCy0TBWikNh
92A2RDQcqSa8GM2wPGohIJEseXSEB0NGjvpnihbBzYIKnupIk0iGjJFwnGo/C6gl
rseVk/CIE4QsATQqhW6bUzUhZpXTSgeh+Wb+aspjgzZif7ttkeeaGnlSOwt1efNl
Rg5ONSJLMOv3g4kvBApQgJgnEYt3+86R9MgriKKCUUGJDMHQTumTfWJB+LSViqYe
TLq9LEwADqcW/mYwcbuKOs6SL4trapqJqYjYkQiR1paVM0EC8oqaBNsy8bmCHIXQ
xgqRPATukWmlavMr2MpVpuFcbvGv0gHOh3qUePUS3TmA/nQI0uh3WpflZb26Io3Q
uSMlK1I3tXGaPTiRYwJjS24ptV0y1XjCrZQvBwW4HO4SwzajSJOH5emJ2Ce0nYCl
FVwyZG+LnKhxm0nH7kVLiOH/+XBdPSd/YuTAV4UoLSGBD3VDbhVpiVKnTOzSyk0z
mOg6DxYGKRDqeGziHG4BxlJUU+MH88U+wwI08YK7i3z/7pLnmzZ52BBnGPbh0oci
/9Y8Kr+isVeGu5FmDe38qe01kodkSTohaZR9fSWgiLIDfD+U/kK+J6KEJZBHiSbL
dN+G6XDmJ17Nav/GKsLC
=D38s
-----END PGP SIGNATURE-----

[py3.debdiff (text/x-diff, attachment)]

Message #10 received at 729924@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: Barry Warsaw <barry@debian.org>, 729924@bugs.debian.org

Subject: Re: Bug#729924: vim: Add Python 3 support

Date: Fri, 31 Jan 2014 23:04:21 -0500

[Message part 1 (text/plain, inline)]

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.

This is due to two things.

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.

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 both versions, my understanding is that the
RTLD_GLOBAL issue still exists.  This means I still need to choose one
version and, while it's more of a toss up now, I think Python 2 is still
the right call here.

Second, I'm not keen on the state of dependency tracking with software
that dynamically loads libraries instead of linking against them.  If
Vim dynamically loaded its own code that provides the language bindings,
and those were linked against the proper language libraries, then I
could easily provide vim-{lua,perl,python,ruby,tcl}-bindings packages
which expressed proper relationships on the corresponding language
libraries.

Since that isn't the case, we can then run into situations where bad
things happen during a library transition due to nothing telling the
transition trackers that Vim should actually be rebuilt or forcing the
users to upgrade Vim in sync with the library.  See #611573 for some
previous discussion about this related to Vim's Perl support.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 729924@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: James McCoy <jamessan@debian.org>

Cc: 729924@bugs.debian.org

Subject: Re: Bug#729924: vim: Add Python 3 support

Date: Mon, 3 Feb 2014 17:38:12 -0500

[Message part 1 (text/plain, inline)]

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?

[signature.asc (application/pgp-signature, attachment)]

Message #20 received at 729924@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: Barry Warsaw <barry@debian.org>, 729924@bugs.debian.org

Subject: Re: Bug#729924: vim: Add Python 3 support

Date: Mon, 3 Feb 2014 19:31:40 -0500

[Message part 1 (text/plain, inline)]

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().  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.

The user doesn't necessarily have a choice in the matter.  If they find
plugins A and B that they want to use, but one is implemented in Python 2
and the other in Python 3, then they're either a) running Debian and out
of luck, b) running a distro that doesn't require RTLD_GLOBAL and
happy, or c) trying to convince one of the plugin authors to port their
plugin.

> 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!

I was part of some discussion[0] on the vim-dev list when this was being
fleshed out that shows it does work.  The problem is that Debian's
python builds don't link the C extensions against the relevant libpython.

> 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?

That's essentially what already happens with dynamic loading enabled,
except the "user selection" is a matter of "run either :python or
:python3 before Python-using plugins are loaded to force the bindings
you want to be loaded."

From my maintainer perspective, the bigger issue is the lack of
traceability of dependencies to aid binNMUs and the like.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 729924@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: Barry Warsaw <barry@debian.org>, 729924@bugs.debian.org

Subject: Re: Bug#729924: vim: Add Python 3 support

Date: Mon, 3 Feb 2014 19:38:58 -0500

[Message part 1 (text/plain, inline)]

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 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!
> 
> I was part of some discussion[0] on the vim-dev list when this was being
> fleshed out that shows it does work.  The problem is that Debian's
> python builds don't link the C extensions against the relevant libpython.

[0]: http://article.gmane.org/gmane.editors.vim.devel/27270

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 729924@bugs.debian.org (full text, mbox, reply):

From: David Mohr <bugs@da.mcbf.net>

To: 729924@bugs.debian.org

Subject: Ping

Date: Thu, 20 Nov 2014 10:11:31 -0700

Hi,

I just wanted to say that this is an active issue for me. I am 
developing code in Python 3, and python-mode etc don't work when started 
with Python 2 since then they don't recognize the Python 3 syntax. While 
Python 2 is still in widespread use, Python 3 usage is rising and it is 
a shame that vim can't handle it out of the box.

I don't have time to actively work on this issue, but I'd be more than 
happy to test any patches.

Thanks,
~David

Message #35 received at 729924@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: David Mohr <bugs@da.mcbf.net>, 729924@bugs.debian.org

Subject: Re: Bug#729924: Ping

Date: Fri, 21 Nov 2014 23:42:40 -0500

[Message part 1 (text/plain, inline)]

On Thu, Nov 20, 2014 at 10:11:31AM -0700, David Mohr wrote:
> I just wanted to say that this is an active issue for me. I am developing
> code in Python 3, and python-mode etc don't work when started with Python 2
> since then they don't recognize the Python 3 syntax. While Python 2 is still
> in widespread use, Python 3 usage is rising and it is a shame that vim can't
> handle it out of the box.

Vim can, but not the way Debian currently packages libpython.  Also,
given the reasons I've already stated in this bug, enabling Vim's
dynamic loading of language bindings isn't something that I think is an
acceptable middle ground even though it would give a little more leeway
in your situation.

> I don't have time to actively work on this issue, but I'd be more than happy
> to test any patches.

Unfortunately, I don't have any patches that can be tested.  It either
requires changing how libpython is packaged or seriously overhauling how
Vim implement dynamic loading of its language bindings.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 729924@bugs.debian.org (full text, mbox, reply):

From: Bernard Pratz <bernard@pratz.net>

To: 729924@bugs.debian.org

Subject: Re: Bug#729924: vim: Add Python 3 support

Date: Tue, 25 Nov 2014 11:27:56 +0100

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 IMproved 7.4 (2013 Aug 10, compiled Nov 11 2014 21:41:52)
Included patches: 1-488
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by guyzmo@BuGz.eclipse.m0g.net
Huge version with GTK2 GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
+balloon_eval    +float           +mouse_urxvt     -tag_any_white
+browse          +folding         +mouse_xterm     +tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
+clientserver    -hangul_input    +netbeans_intg   +title
+clipboard       +iconv           +path_extra      +toolbar
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      +python3/dyn     +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con_gui  +lua             +rightleft       +windows
+diff            +menu            +ruby            +writebackup
+digraphs        +mksession       +scrollbind      +X11
+dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     +xim
+emacs_tags      +mouseshape      -sniff           +xsmp_interact
+eval            +mouse_dec       +startuptime     +xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    +xpm
[…]
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
-I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12     -g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-I/usr/include/tcl8.5  -D_REENTRANT=1  -D_THREAD_SAFE=1
-D_LARGEFILE64_SOURCE=1  
Linking: gcc   -L. -Wl,-z,relro -rdynamic -Wl,-export-dynamic -Wl,-E
-fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
-lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype
-lfontconfig -lgobject-2.0 -lglib-2.0   -lSM -lICE -lXpm -lXt -lX11
-lXdmcp -lSM -lICE  -lm -ltinfo -lelf -lnsl  -lselinux   -lacl -lattr
-lgpm  -L/usr/lib -llua5.2 -Wl,-E  -fstack-protector -L/usr/local/lib
-L/usr/lib/perl/5.14/CORE -lperl -ldl -lm -lpthread -lcrypt   -L/usr/lib
-ltcl8.5 -ldl -lpthread -lieee -lm -lruby-1.9.1 -lpthread -lrt -ldl
-lcrypt -lm  -L/usr/lib   
-------->8---------------->8---------------->8--------------->8--------

I did not run into any issue so far, though when I try to run both
python 2 and python 3 from ex command line:

--------8<----------------8<----------------8<---------------8<--------
:py import sys;print(sys.version)
2.7.3 (default, Mar 13 2014, 11:26:58) 
[GCC 4.7.2]
:py3 import sys;print(sys.version)
E837: This Vim cannot execute :py3 after using :python
E263: Sorry, this command is disabled, the Python library could not be
loaded.
-------->8---------------->8---------------->8--------------->8--------

Which is a nice explicit error! I'm also in favour of switching to
python3 which is mature enough and should replace python2 everywhere it
can.

So I do believe the dual compilation option is the best option, as you
leave it to the user to make sure his whole configuration is being run
using one or the other. But to promote transition to py3, the software
package needs to be able to load py3 components!

Cheers,

-- 
Bernard Pratz

Message #45 received at 729924@bugs.debian.org (full text, mbox, reply):

From: Diederik de Haas <diederik@cknow.org>

To: 729924@bugs.debian.org

Subject: Re: Bug#729924: vim: Add Python 3 support

Date: Thu, 14 Jan 2016 17:13:07 +0100

[Message part 1 (text/plain, inline)]

On Fri, 31 Jan 2014 23:04:21 -0500 James McCoy <jamessan@debian.org> 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 both versions, my understanding is that the
> RTLD_GLOBAL issue still exists.  This means I still need to choose one
> version and, while it's more of a toss up now, I think Python 2 is still
> the right call here.

Do you think it is still the right call or has the time come to switch to 
Python 3? 
Your call is now almost 2 years old and if you'd like Stretch to have Python 3 
support, now seems like a good time to make the switch so there's plenty of 
time to catch and fix bugs if the switch would trigger that.

Cheers,
  Diederik

[signature.asc (application/pgp-signature, inline)]

Message #50 received at 729924@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: 729924@bugs.debian.org

Subject: Default to Python3 builds, add Python2 variants

Date: Wed, 6 Apr 2016 12:21:33 +0200

[Message part 1 (text/plain, inline)]

Hi,

please find attached a debdiff which builds with Python3 as the default, and 
adds Python2 variants as extra packages.  I worked with the ycmd amd 
vim-youcompleteme maintainer to test these packages in Ubuntu.  Ubuntu's 
motivation was to get rid off Python2 from some CD images, defaulting to 
Python3.  People still can install the -py2 variants, but it would be nice to 
move to Python3 by default in vim for the next Debian release as well.

Matthias

PS: I left the ubuntu patches in the diff, at least for the unsupported status 
of trusty, the Debian package is doing it wrong.

PPS: The python extensions are not linked against libpython to avoid 
dependencies on more than one Python version when we have more than one 
Python3.x version in the archive.

[py3.diff (text/x-diff, attachment)]

Message #55 received at 729924@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: Matthias Klose <doko@debian.org>, 729924@bugs.debian.org

Subject: Re: Bug#729924: Default to Python3 builds, add Python2 variants

Date: Sun, 24 Apr 2016 00:19:01 -0400

On Wed, Apr 06, 2016 at 12:21:33PM +0200, Matthias Klose wrote:
> please find attached a debdiff which builds with Python3 as the default, and
> adds Python2 variants as extra packages.

I understand the desire to have Python3 support, but I'm not keen on
creating separate Python2 and Python3 packages.

From an initial look, it seems like the only packaged addons that
require Python support both 2 & 3.  Maybe it's time to just switch to
Python3.  I guess the sooner that happens before the release, the more
chance there is for people to complain about broken stuff.

> PS: I left the ubuntu patches in the diff, at least for the unsupported
> status of trusty, the Debian package is doing it wrong.

Yeah, not sure why I moved trusty.  Must've gotten trusty and vivid
confused.  I've fixed that, as well as added yakkety.

> PPS: The python extensions are not linked against libpython to avoid
> dependencies on more than one Python version when we have more than one
> Python3.x version in the archive.

Thanks for explaining the reasoning.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>

Message #60 received at 729924@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: Matthias Klose <doko@debian.org>, 729924@bugs.debian.org

Cc: Barry Warsaw <barry@debian.org>

Subject: Re: Bug#729924: Default to Python3 builds, add Python2 variants

Date: Mon, 8 Aug 2016 18:25:53 -0400

On Sun, Apr 24, 2016 at 12:19:01AM -0400, James McCoy wrote:
> On Wed, Apr 06, 2016 at 12:21:33PM +0200, Matthias Klose wrote:
> > please find attached a debdiff which builds with Python3 as the default, and
> > adds Python2 variants as extra packages.
> 
> I understand the desire to have Python3 support, but I'm not keen on
> creating separate Python2 and Python3 packages.
> 
> From an initial look, it seems like the only packaged addons that
> require Python support both 2 & 3.  Maybe it's time to just switch to
> Python3.

If there are no objections, I'm going to make this change in the next
upload.

> I guess the sooner that happens before the release, the more
> chance there is for people to complain about broken stuff.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Message #65 received at 729924-submitter@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: 729924-submitter@bugs.debian.org

Subject: Bug#729924 marked as pending

Date: Wed, 31 Aug 2016 04:00:41 +0000

tag 729924 pending
thanks

Hello,

Bug #729924 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

    http://git.debian.org/?p=pkg-vim/vim.git;a=commitdiff;h=6e543c2

---
commit 6e543c265292524b545358c0def3f9f45d6744ae
Author: James McCoy <jamessan@debian.org>
Date:   Mon Aug 8 01:09:33 2016 -0400

    Switch Python language bindings from 2 to 3
    
    Closes: #729924
    Signed-off-by: James McCoy <jamessan@debian.org>

diff --git a/debian/changelog b/debian/changelog
index c96ef50..f3fbe49 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,8 @@ vim (2:7.4.2181-1) UNRELEASED; urgency=medium
           (Closes: #827634)
       - runtime/syntax/rst.vim:
         + Use underline for emphasized text.  (Closes: #547537)
+  * Switch from Python2 to Python3 language bindings.  All packaged
+    addons which use Python support both 2 & 3.  (Closes: #729924)
 
  -- James McCoy <jamessan@debian.org>  Sun, 07 Aug 2016 23:46:52 -0400
 

Message #70 received at 729924-close@bugs.debian.org (full text, mbox, reply):

From: James McCoy <jamessan@debian.org>

To: 729924-close@bugs.debian.org

Subject: Bug#729924: fixed in vim 2:7.4.2330-1

Date: Thu, 08 Sep 2016 04:32:29 +0000

Source: vim
Source-Version: 2:7.4.2330-1

We believe that the bug you reported is fixed in the latest version of
vim, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 729924@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy <jamessan@debian.org> (supplier of updated vim package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 07 Sep 2016 22:12:11 -0400
Source: vim
Binary: vim-common vim-gui-common vim-runtime vim-doc vim-tiny vim vim-gtk vim-gtk3 vim-nox vim-athena vim-gnome
Architecture: source
Version: 2:7.4.2330-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Vim Maintainers <pkg-vim-maintainers@lists.alioth.debian.org>
Changed-By: James McCoy <jamessan@debian.org>
Description:
 vim        - Vi IMproved - enhanced vi editor
 vim-athena - Vi IMproved - enhanced vi editor - with Athena GUI
 vim-common - Vi IMproved - Common files
 vim-doc    - Vi IMproved - HTML documentation
 vim-gnome  - Vi IMproved - enhanced vi editor (dummy package)
 vim-gtk    - Vi IMproved - enhanced vi editor - with GTK2 GUI
 vim-gtk3   - Vi IMproved - enhanced vi editor - with GTK3 GUI
 vim-gui-common - Vi IMproved - Common GUI files
 vim-nox    - Vi IMproved - enhanced vi editor - with scripting languages suppo
 vim-runtime - Vi IMproved - Runtime files
 vim-tiny   - Vi IMproved - enhanced vi editor - compact version
Closes: 547537 729924 788055 820239 827634 830545 834336
Changes:
 vim (2:7.4.2330-1) unstable; urgency=medium
 .
   [ upstream ]
   * Highlighted changes:
     + 7.4.1976: Support 64-bit number variables in VimL.  Use has('num64') to
       test for presence of the functionality.  (Closes: #788055)
     + runtime/ftplugin/man.vim:
       - Use the width of the current window when formatting a man page.
         (Closes: #827634)
     + runtime/syntax/rst.vim:
       - Use underline for emphasized text.  (Closes: #547537)
     + runtime/tutor/tutor.es:
       - Fix misspelling of seguido.  (Closes: #834336)
 .
   [ James McCoy ]
   * Switch from Python2 to Python3 language bindings.  All packaged
     addons which use Python support both 2 & 3.  (Closes: #729924)
   * Add mips64el as a recognized architecture in debcontrol files.  Thanks to
     Reiner Herrmann for the patch.  (Closes: #830545)
   * Update supported Ubuntu releases in debsources files.
   * Remove vim-gnome (which uses deprecated gnome2 libraries) in favor of
     vim-gtk3.  (Closes: #820239)
   * Run tests during build targets to avoid test failures related to running
     as (fake)root.
Checksums-Sha1:
 e8377add87c0f2fe081981066e22dc97cdb531d3 2917 vim_7.4.2330-1.dsc
 bcafe89c2ebcc67e9a59c05f0457b9d8d9b28348 12910761 vim_7.4.2330.orig.tar.gz
 60564ebdb85776c534fcdb8761801600a39c0eda 189616 vim_7.4.2330-1.debian.tar.xz
Checksums-Sha256:
 c74a332212b1d4c680213eb4d94044dd17d6e20bed9aeb4732dcd3d34ca9f190 2917 vim_7.4.2330-1.dsc
 90e242e7d463b2d85a695398d8f19d7ba25f08a4a3405bb3fb76d91128021e2f 12910761 vim_7.4.2330.orig.tar.gz
 3b416c0d45317475747b9744d846acab78094194edd3b698e00e2e4b3a2d63d6 189616 vim_7.4.2330-1.debian.tar.xz
Files:
 ccc1c5059f0c3da761428c5784424ef9 2917 editors optional vim_7.4.2330-1.dsc
 25dba84be2b7a0146e218ce43a56e015 12910761 editors optional vim_7.4.2330.orig.tar.gz
 75c1e72261c8ea084501788586c37cdf 189616 editors optional vim_7.4.2330-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJX0M0BXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MUJGQkY0RDY5NTZCRDVERjdCNzJEMjNE
RkU2OTFBRTMzMUJBM0RCAAoJEN/mka4zG6PbUP4P/j0tIy/C1ld7UbHA842tFJhT
R+KSLDIJrehzxr4/BhaZkd5yVLaC2VbOB+lgUyMRJdm5xfK8omdGhFKDSmC/fqVW
VT/WS9Kh8BQO49eczk3HCluR83ng4V0vTukH7MdqMvOfiXlALdSU8nrBe5Fmrq2+
/AFKxjrQpqTFcOM9fEUGAzIVW1AB1kvuvpnaLYhVx26bizzI2v0OnMWR4Sv+dpzq
HiePa8SMEWmevw0jCd+mkfKXv/vMvU/cVmYx/TCOpJdHGjCXkGE2qw/w/0zXAKFN
CTHH1P5yHFffju+xiDjQyfrSSWOF22ikGETVlDQvUdkpDXeFKUIbRFiEBxO8gzbp
QpOOu2pP3ozYK02PbuZOQP7eDK7LFwZXiHHE4HgOdWGkpL5gqBNwg8ijWbVL87xD
5jGTAHZOsyLJUI9t3kTZZxsTVYtzkdvdvZ7pGwEOZR4fRpXV97f1icsUcDFPnx3Y
Z3GSlpYq3LmEn9N/hGaolevT1dd5c98jLUarTY+8+23cSEHfrwd2X4iKOrAA/Cxf
l2f0GPdsuoMlhZc7lIQZOKQIhZsJoITv6WWTozPh+UQmwXghZjEmnHQJlWZIin8L
FXcEXriYJ0E+E/SeDnftX5KHgDkBggXmK/Wwgf63NUSUlEmEqwk4gK1GpleBq9/J
YT/smMjIzzsO3k7cUcKG
=P8fm
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.