From: Eli Zaretskii <eliz@gnu.org>
To: fgallina@gnu.org (Fabián Ezequiel Gallina)
Cc: 18596@debbugs.gnu.org
Subject: bug#18596: 25.0.50; MS-Windows needs a different default for python-shell-interpreter-args
Date: Mon, 17 Nov 2014 05:38:41 +0200 [thread overview]
Message-ID: <83ioiecx8e.fsf@gnu.org> (raw)
In-Reply-To: <87ioiezw00.fsf@gnu.org>
> From: fgallina@gnu.org (Fabián Ezequiel Gallina)
> Cc: 18596@debbugs.gnu.org
> Date: Sun, 16 Nov 2014 18:16:47 -0300
>
> > Thanks. But
> >
> > M-: (run-python (executable-find "python") nil) RET
> >
> > still hangs for me on MS-Windows. What am I missing?
> >
>
> I believe we agreed on the fix being that the defaults should not hang.
Indeed. Trouble is, it still does.
> The fact that your example hangs on Window is bad but it's not worth the
> trouble of mangling the provided command and trying to add the "-i"
> switch to it as it would break other cases.
We can add -i as long as the caller didn't provide a command. I see
nothing wrong with this. If you do, please explain why is it wrong.
Which other use cases will it break?
> >From the Python help:
>
> -i : inspect interactively after running script; forces a prompt even
> if stdin does not appear to be a terminal; also PYTHONINSPECT=x
>
> So I tried a solution that was ought to leave everyone happy, which was
> setting PYTHONINSPECT env variable before run-python, but that didn't
> help on Windows either. If you have other ideas I'm eager to try them
> out.
I had another idea to begin with: add -i. I also tested it and found
it to work in the use case I presented.
Thanks.
prev parent reply other threads:[~2014-11-17 3:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 15:12 bug#18596: 25.0.50; MS-Windows needs a different default for python-shell-interpreter-args Eli Zaretskii
2014-10-01 16:48 ` Glenn Morris
2014-10-01 16:50 ` Eli Zaretskii
2014-10-03 0:51 ` Fabián Ezequiel Gallina
2014-10-03 8:15 ` Eli Zaretskii
2014-10-16 10:22 ` Eli Zaretskii
2014-11-14 7:25 ` Fabián Ezequiel Gallina
2014-11-14 10:38 ` Eli Zaretskii
2014-11-14 13:05 ` Fabián Ezequiel Gallina
2014-11-14 14:29 ` Eli Zaretskii
2014-11-14 16:01 ` Fabián Ezequiel Gallina
2014-11-14 16:50 ` Eli Zaretskii
2014-11-14 20:55 ` Fabián Ezequiel Gallina
2014-11-14 21:04 ` Eli Zaretskii
2014-11-15 0:29 ` Stefan Monnier
2014-11-15 7:37 ` Eli Zaretskii
2014-11-16 14:21 ` Fabián Ezequiel Gallina
2014-11-16 15:45 ` Eli Zaretskii
2014-11-16 21:16 ` Fabián Ezequiel Gallina
2014-11-17 3:38 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ioiecx8e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18596@debbugs.gnu.org \
--cc=fgallina@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).