all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Strip <david@stripfamily.net>
Cc: emacs-devel@gnu.org
Subject: Re: Bug in python.el (at least for Windows OS)
Date: Sat, 06 Dec 2014 10:04:56 +0200	[thread overview]
Message-ID: <83lhml19w7.fsf@gnu.org> (raw)
In-Reply-To: <548288E4.2030302@stripfamily.net>

> From: David Strip <david@stripfamily.net>
> Date: Sat, 06 Dec 2014 04:41:16 +0000
> 
> If the path to the python executable contains an embedded space, any command
> that attempts to spawn a shell will fail with "invalid argument" since the
> space makes the command appear to contain extra args.
> In some sense, the root of the problem is locate-file, called by
> executable-find (both defined in files.el). locate-file does not return quoted
> paths. I'm not sure if the best fix is at the locate-files level, since I'm not
> sure what consequences this might have elsewhere, esp on non-Windows OS's. The
> most localized fix would be in python.el, changing python-shell-parse-command
> to add the required quotes. In the simplest case, this would be just change the
> format statement from
> 
>     (format "%s %s"
>     
> 
> to
> 
>     (format "\"%s\" %s"
>     
> 
> This definitely works on Windows, but I'm not certain how this would affect
> other OS's. Perhaps the format string has to be conditioned on the OS.

Thanks.  Please submit a bug report about that, using the
'report-emacs-bug' command.  If you do that from the same version of
Emacs where you have the problem, the command will collect some
auxiliary information that the maintainers need to be able to diagnose
and solve the problem.

TIA



      reply	other threads:[~2014-12-06  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-06  4:41 Bug in python.el (at least for Windows OS) David Strip
2014-12-06  8:04 ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lhml19w7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=david@stripfamily.net \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.