[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#678122: marked as done (vim-gnome: python bindings botched?)

Your message dated Mon, 10 Sep 2012 16:00:17 +0200
with message-id <504DF271.5050502@ubuntu.com>
and subject line closing, not a gcc bug, but a bug in vim
has caused the Debian Bug report #678122,
regarding vim-gnome: python bindings botched?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
678122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678122
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: vim-gnome
Version: 2:7.3.547-1
Severity: normal

With vim 2:7.3.547-1 and the implied python2.7 the python bindings are broken
in some way - although I cannot say whether it's vim or pythons fault.

With 2:7.2.330-1ubuntu3 I get the correct result:

# vim -u NONE -U NONE -N -c "python sys.stdout.write('1')" -c ':q!'
1
# vim -u NONE -U NONE -N -c "python sys.stdout.write(1)" -c ':q!'
Error detected while processing command line:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: argument 1 must be string or read-only buffer, not int
#


But with the current debian version both are silent.
# vim -u NONE -U NONE -N -c "python sys.stdout.write(1)" -c ':q!'
#

This breaks any vim plugin that uses "print" or "sys.stdout.write"; I found
that via slimv.


I tried to use libpython2.6 (via a symlink from libpython2.7.so), but the
behavior didn't change; so I guess it's rather on vim's side.


Downgrading to 2:7.2.445+hg~cb94c42c0e1a-1 would break other dependencies, so I
didn't test.
I think it did work with 2:7.3.429-2, but I'm not sure about that -- is it
still available somewhere?



-- Package-specific info:

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

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-gnome depends on:
ii  libacl1             2.2.51-7
ii  libbonoboui2-0      2.24.3-1
ii  libc6               2.13-33
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-0        2.32.3-1
ii  libgnome2-0         2.32.1-2
ii  libgnomeui-0        2.24.5-2
ii  libgpm2             1.20.4-6
ii  libgtk2.0-0         2.24.10-1
ii  libice6             2:1.0.8-2
ii  liblua5.1-0         5.1.5-2
ii  libpango1.0-0       1.30.0-1
ii  libperl5.14         5.14.2-11
ii  libpython2.7        2.7.3-1
ii  libruby1.9.1        1.9.3.194-1
ii  libselinux1         2.1.9-2
ii  libsm6              2:1.2.1-2
ii  libtinfo5           5.9-8
ii  libx11-6            2:1.4.99.901-2
ii  libxt6              1:1.1.3-1
ii  tcl8.5              8.5.11-2
ii  vim-common          2:7.3.547-1
ii  vim-gui-common      2:7.3.547-1
ii  vim-runtime         2:7.3.547-1

vim-gnome recommends no packages.

Versions of packages vim-gnome suggests:
ii  cscope            15.7a-3.6
ii  gnome-icon-theme  3.4.0-2
ii  ttf-dejavu        2.33-2
pn  vim-doc           <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
closing, not a gcc bug, but a bug in vim

--- End Message ---
Reply to: