From: fgallina@gnu.org (Fabián Ezequiel Gallina)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18596@debbugs.gnu.org
Subject: bug#18596: 25.0.50; MS-Windows needs a different default for python-shell-interpreter-args
Date: Fri, 14 Nov 2014 17:55:40 -0300 [thread overview]
Message-ID: <87wq6xo62b.fsf@gnu.org> (raw)
In-Reply-To: <83wq6xhgk3.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Nov 2014 18:50:52 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: fgallina@gnu.org (Fabián Ezequiel Gallina)
>> Cc: bug-gnu-emacs@gnu.org
>> Date: Fri, 14 Nov 2014 13:01:45 -0300
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>> >>
>> >> I can only recreate the hang if I remove the "-i" switch in the default
>> >> command, so I think the real issue here is to fix how tests define the
>> >> command to run rather than changing the defaults on python.el. With
>> >> this said, I think this bug should be closed and we should move to
>> >> #18595.
>> >
>> > Are you saying that it is OK for the above form to hang?
>> >
>>
>> Yes, on Windows the "-i" switch is required to avoid the hang and M-x
>> run-python does the right thing adding it by default.
>
> I know that "M-x run-python" does that, but I think run-python itself
> should do that, too. It's a bug for it to hang like that.
>
I don't agree, run-python will run whatever you tell it to run and while
I agree that malformed commands hanging it are not fun, that's the very
same reason why sane defaults are provided and why the commentary
section state possible problems clearly.
>> We just need to fix the tests so they don't forget about "-i".
>
> That's a related, but separate problem.
>
I'll focus on that alone, I'm still not convinced on the course of
action for this one.
next prev parent reply other threads:[~2014-11-14 20:55 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 [this message]
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
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=87wq6xo62b.fsf@gnu.org \
--to=fgallina@gnu.org \
--cc=18596@debbugs.gnu.org \
--cc=eliz@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).