Package: python-mode
Version: 1:6.0.10-1
Severity: important
Tags: upstream

Just placing it into Debian BTS so we do not loose track what ideally
should get fixed to get python mode into usable state for the release

I thought that before (with one of the tentative debian packages) I have
managed to make it convenient -- that I split the window to have in one
buffer the code and in another ipython shell, so that C-! jumps into
ipython, and C-c C-c sends buffer to ipython shell but everything remains as is
-- just 2 buffers visible.

Now with 1:6.0.10-1 it is chaos for me

- if I disable splitting and shell-switch-buffers-on-execute is off -- it would 
maximize code buffer thus hiding all other visible before
- if -focus- is on -- then it works only if I have split into 2 ... if I had 
more splits -- only 2 survive upon C-c C-c and it might be not the actual 
buffer with code sent which would be visible after C-c C-c

- If I enable splitting -- it becomes complete mad possibly making more splits, 
or making other splits show the buffer which I have sent with C-c C-c

See
https://bugs.launchpad.net/python-mode/+bug/1018996
for more details/discussion with upstream

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'stable')
Architecture: amd64 (x86_64)

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

Versions of packages python-mode depends on:
ii  emacs [emacsen]    23.3+1-1
ii  emacs23 [emacsen]  23.4+1-3
ii  python             2.7.2-10
ii  python2.6          2.6.7-4
ii  python2.7          2.7.3~rc2-2.1

Versions of packages python-mode recommends:
ii  pychecker  0.8.19-3
ii  pymacs     0.23-1.1

Versions of packages python-mode suggests:
ii  pylint           0.24.0-1
ii  python-ropemacs  0.6c2-4

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to