Barry Warsaw | 13 Mar 22:16 2015

Re: Displaying symbols in customization buffer

On Mar 13, 2015, at 07:54 PM, Andreas Röhler wrote:

>Currently it looks strange - see attachment.

Agreed, but what can python-mode do about that?  It's just the way Emacs'
customize feature works.


Python-mode mailing list
Python-mode <at>
Andreas Röhler | 13 Mar 15:51 2015

Displaying symbols in customization buffer

Hi Barry, hi all,

currently most of symbols in customization buffer get splitted, resulting parts are capitalized.

Would prefer to display it with real name, which permits searching it.

Any opinion about that?


andrea crotti | 31 Jan 21:58 2015


Hi guys, I just reinstalled everything from scratch and loading
python-mode gives me this error below..
The file in fact does not exist anywhere so not sure how it was
working before, any idea where it should be?

Debugger entered--Lisp error: (file-error "Cannot open load file" "no
such file or directory" "python-components-switches")
  eval-buffer(#<buffer  *load*≥ nil
nil t)  ; Reading at buffer position 90348
nil nil)
  call-interactively(load-library record nil)
  command-execute(load-library record)
  execute-extended-command(nil "load-library")
  call-interactively(execute-extended-command nil nil)
andrea crotti | 7 Jan 11:46 2015

Python help buffer

Hi guys,

I have a problem with Emacs 25 that does not happen with Emacs 24.4.
More specifically with:
- GNU Emacs (x86_64-apple-darwin13.4.0, NS appkit-1265.21
Version 10.9.5 (Build 13F34)) of 2014-11-15 on
- Python mode: 6.1.3

So in short with Emacs 25 the *Python Help* buffer keeps coming up,
whenever the cursor stays for more than a second on something.

I digged a bit and it seems to come from the "py-help-at-point"
function, can't understand why it does not happen with Emacs 24.4.

I thought it was related to Eldoc but that's also disabled so it's not
the case, and I can't find any variable to customize to disable that
once for all..
I guess it's just something changed in Emacs 25 but can't find out what :/
Any idea?

Doing a "(defun py-help-at-point nil)" works of course but it's not the
desired solution since it's still useful sometimes.

Thanks a lot
Andreas Röhler | 28 Nov 20:30 2014

python-mode.el-6.2.0 released

Hi Barry, hi all,

so it's out there finally.

For new features see


Andreas Röhler | 30 Sep 08:51 2014

Re: [Bug 1375122] Re: py-indent-line behavior from 6.1.1

On 29.09.2014 23:02, Jonathan C. Dodd wrote:
> Unfortunately, C-j is only possible from the previous line, and I tend
> to jump around the code quite a bit.  When I come back wanting to e. g.
> insert a new line into a matrix, I have to either go to the line before
> the one I have inserted and press C-j from there, or press TAB
> repeatedly and align the remainder with spaces.  This is completely
> unintuitive and inconsistent relative to other modes (c++-mode, js-mode,
> emacs-lisp-mode etc etc, which all move cursor to rightmost sane
> indentation when pressing TAB).

Seeing you point. However, the way it behaves now is the default for years.

May change the behaviour so jumps to outmost with first TAB, stepping
backwards afterwards.

Or have another boolean and customization?
Barry, WDYT?

Will cc it to python-mode mailing-list.
Andreas Röhler | 1 Sep 18:02 2014

Completion of symbols defined in current buffer

Hi Barry,

being inclined to drop that feature

Emacs provides dabbrev-expand, which is Python-agnostic but fairly effectiv.
Otherwise the buffers content needs to be evaluated - with means, it must be correct already.


Andreas Röhler | 30 Jun 09:12 2014

py-shell-name no longer buffer-local


as difficulties have been reported WRT py-shell-name and the like being buffer-local, consider to drop
that, making them normal vars.

Just FYI, please tell if any objections,

Andreas Röhler | 25 Jun 16:04 2014

TAB in script buffer


lately TAB in Python shell was bound to `py-shell-complete-or-indent'.

What about doing likewise in script buffers - where TAB is currently `py-indent-line'?

Unfortunatly the default completion-key M-TAB is used by most X-windows systems, so users must
re-configure first.

Binding it to TAB would solve that.

BTW in this case completion should only be called at end of line and with word before. Otherwise TAB would
`py-indent-line' - as a second TAB would do also.



Andreas Röhler | 14 Jun 17:29 2014

Reduce complexity

Hi Barry, hi all,


consider to drop two variables, which introduce complexity while not being that useful as expected.



which would insert a TAB if no completion is found.

The other:


`dabbrev-expand' is a well known feature at its own keys,
IMO doesn't pay to instrument it here.

Just FYI.

Should anybody want to keep the variables mentioned, please tell.


Andreas Röhler | 2 Jun 09:06 2014

TAB-completion in Python shell

Hi Barry, hi all,

completion in py-shell always was M-TAB

However, many people switching to python-mode.el expect TAB to complete there.

Here one from a bunch of reports:

Any suggestions?