It seems to me that this is primarily not an upstream issue but
a problem of the Debian package itself.
The pylint upstream Python package does not install any non-standard
Emacs key bindings. It only provides en elisp file with code (function
'pylint-add-key-bindings') that will do so if called and a comment that
invites users to add this function to their config.
It’s the Debian packaging that adds a file
(/etc/emacs/site-start.d/50pylint.el) that will execute said function on
Emacs startup by default.
For myself, I work around this issue by calling (remove-hook
'python-mode-hook 'pylint-add-key-bindings) in my emacs init file.
But it would be IMHO preferable if this was not necessary and
pylint-add-key-bindings would no longer be executed by default by the
Debian package.
The key binding to run pylint (C-c m l) is not necessary anyway since
Emacs default python mode already defines C-c C-v ('python-check') that
will run (e)pylint if it is installed (and if pyflakes is not). The
preferred checking command can be configured through the variable
'python-check-command'.
The other bindings, 'C-c m n' and 'C-c m p' are just alternative
bindings for next-error and previous-error that already have global key
bindings anyway.
Finally, pylint-insert-ignore-comment ('C-c m i') is a command that
tends to be used less regularly and does not require a default key
binding. It can be called from the menu or by typing 'M-x p-i-i-c'.
