(py-electric-backspace): I'm not sure this function should be special

casing when py-honor-comment-indentation is nil, but this could be a
religious issue with some.  Seems to me we should still be dedenting
such comment lines one level.

diff --git a/Misc/python-mode.el b/Misc/python-mode.el
index a62e17378b6093efd05bddd142599e2a6df0bd73..924c2c703212deddfcbba8176c63f8abf31d94d7 100644 (file)
--- a/Misc/python-mode.el
+++ b/Misc/python-mode.el
@@ -1524,8 +1524,8 @@ zero).
 
 Otherwise the preceding character is deleted, converting a tab to
 spaces if needed so that only a single column position is deleted.
-\\[universal-argument] specifies how many characters to delete
-(default is 1).
+\\[universal-argument] specifies how many characters to delete;
+default is 1.
 
 When used programmatically, argument ARG specifies the number of
 blocks to dedent, or the number of characters to delete, as indicated
@@ -1534,8 +1534,9 @@ above."
   (if (or (/= (current-indentation) (current-column))
          (bolp)
          (py-continuation-line-p)
-         (not py-honor-comment-indentation)
-         (looking-at "#[^ \t\n]"))     ; non-indenting #
+;        (not py-honor-comment-indentation)
+;        (looking-at "#[^ \t\n]")      ; non-indenting #
+         )
       (funcall py-backspace-function arg)
     ;; else indent the same as the colon line that opened the block
     ;; force non-blank so py-goto-block-up doesn't ignore it