Noisy interaction with python-mode

[Richard Stanton]

I've started using the EIN package, which allows use of ipython notebooks within Emacs, and it makes use of MuMaMo. If I use python-mode (r1070) as my default python mode, I get repeated errors like this, which keep popping up in my minibuffer:

mumamo-set-major-pre-command: cb:*ein: 8888/analyze*, Wrong type argument: listp, python-saved-check-command
MU:mumamo-idle-set-major-mode: cb=*ein: 8888/analyze*, err=(wrong-type-argument listp python-saved-check-command)
** In buffer *ein: 8888/analyze*
  backtrace()
  mumamo-display-error(mumamo-idle-set-major-mode "cb=%s, err=%s" #<buffer *ein: 8888/analyze*> (wrong-type-argument listp python-saved-check-command))
  byte-code("\301\302\303p$\207" [err mumamo-display-error mumamo-idle-set-major-mode "cb=%s, err=%s"] 5)
  mumamo-idle-set-major-mode(#<buffer *ein: 8888/analyze*> #<window 7 on *ein: 8888/analyze*>)
  apply(mumamo-idle-set-major-mode (#<buffer *ein: 8888/analyze*> #<window 7 on *ein: 8888/analyze*>))
  byte-code("r\301\302H\303H\"\210)\301\207" [timer apply 5 6] 4)
  timer-event-handler([t 0 0 500000 nil mumamo-idle-set-major-mode (#<buffer *ein: 8888/analyze*> #<window 7 on *ein: 8888/analyze*>) idle])


[Richard Stanton (a-stanton)]

The problem seems to be that mumamo is looking at a variable that's defined in python.el but not in python-mode.el. A work-around is

(setq python-saved-check-command nil)