bug#42125: closed (Python mode load failing due to some issue with tramp)

[GNU bug Tracking System]

Your message dated Sun, 18 Oct 2020 01:39:40 +0000
with message-id 
<CADwFkmn66RO4RTvZzYLd2NT-yEM1abENWmwQFeDvQKEiLKLRvw@mail.gmail.com>
and subject line Re: bug#42125: Python mode load failing due to some issue with 
tramp
has caused the debbugs.gnu.org bug report #42125,
regarding Python mode load failing due to some issue with tramp
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
42125: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42125
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Python mode load failing due to some issue with tramp
>
>
>
>
> Date: 
>
> Mon, 29 Jun 2020 10:48:17 -0400 (EDT)
>
>
>
>
> Package: emacs
> Version: 26.3
>
> Python mode load is failing due to some issue with tramp.  Likely a
> loaddefs issue or something similar.  To reproduce, simply visit
> a file with a .py extension.
>
> Stack trace:
>
> Debugger entered--Lisp error: (void-variable tramp-default-user-alist)
>   (member x tramp-default-user-alist)
>   (if (member x tramp-default-user-alist) tramp-default-user-alist (setq 
> tramp-default-user-alist (cons x tramp-default-user-alist)))
>   (let* ((x (cons (concat "\\`" (regexp-opt (quote ("su" "sudo" "doas" "ksu"))) 
> "\\'") (quote (nil "root"))))) (if (member x tramp-default-user-alist) 
> tramp-default-user-alist (setq tramp-default-user-alist (cons x 
> tramp-default-user-alist))))
>   eval-buffer(#<buffer  *load*-849947> nil 
> "/usr/share/emacs/26.3/lisp/net/tramp-sh.el" nil t)  ; Reading at buffer 
> position 15068
>   load-with-code-conversion("/usr/share/emacs/26.3/lisp/net/tramp-sh.el" 
> "/usr/share/emacs/26.3/lisp/net/tramp-sh.el" nil t)
>   require(tramp-sh)
>   eval-buffer(#<buffer  *load*> nil 
> "/usr/share/emacs/26.3/lisp/progmodes/python.el" nil t)  ; Reading at buffer 
> position 12340
>   load-with-code-conversion("/usr/share/emacs/26.3/lisp/progmodes/python.el" 
> "/usr/share/emacs/26.3/lisp/progmodes/python.el" nil t)
>   python-mode()
>   set-auto-mode-0(python-mode nil)
>   set-auto-mode()
>   normal-mode(t)
>   after-find-file(nil t)
>   find-file-noselect-1(#<buffer irkerhook.py> "~/WWW/irker/irkerhook.py" nil 
> nil "~/public_html/irker/irkerhook.py" (5771543 66307))
>   find-file-noselect("~/WWW/irker/irkerhook.py" nil nil t)
>   find-file("~/WWW/irker/irkerhook.py" t)
>   funcall-interactively(find-file "~/WWW/irker/irkerhook.py" t)
>   call-interactively(find-file nil nil)
>   command-execute(find-file)
>
> There's a workaround: deleting (require 'tramp-sh) from early in
> python.el. Of course this disables some remote features.
> -- 
>                 <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
>
> "They that can give up essential liberty to obtain a little temporary 
> safety deserve neither liberty nor safety."
>         -- Benjamin Franklin, Historical Review of Pennsylvania, 1759.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#42125: Python mode load failing due to some issue with tramp
>
>
>
>
> Date: 
>
> Sun, 18 Oct 2020 01:39:40 +0000
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
>
>
>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: esr@thyrsus.com (Eric S. Raymond)
> >> Date: Mon, 29 Jun 2020 10:48:17 -0400 (EDT)
> >>
> >> Package: emacs
> >> Version: 26.3
> >>
> >> Python mode load is failing due to some issue with tramp.  Likely a
> >> loaddefs issue or something similar.  To reproduce, simply visit
> >> a file with a .py extension.
> >>
> >> Stack trace:
> >>
> >> Debugger entered--Lisp error: (void-variable tramp-default-user-alist)
> >>   (member x tramp-default-user-alist)
> >
> > I cannot reproduce this, FWIW.  Is it possible that some file in your
> > ~/.emacs.d directory (or some other init-related feature) gets in the
> > way?
> >
> > P.S.  Did you try this in "emacs -Q"?
>
> More information was requested, but none was given within 15 weeks, so
> I'm closing this bug.
>
> If this is still an issue, please reply to this email (use "Reply to
> all" in your email client) and we can reopen the bug report.
>
>
> --- End Message ---