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 10:05:28 -0300 [thread overview]
Message-ID: <87bnoahqzr.fsf@gnu.org> (raw)
In-Reply-To: <83oasahxss.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Nov 2014 12:38:27 +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 04:25:01 -0300
>>
>> FYI I tested this with Windows 7, Python 3.3, 3.4 and 2.7.8 and wasn't
>> able to replicate it. The interpreter started without hanging.
>
> How did you try this? The recipe that (still) hangs for me is the one
> used by the test suite:
>
> (run-python (executable-find "python") nil)
>
I tried this one by starting the interpreter as a user would and since
the "-i" is in the default interpreter arguments the shell doesn't hang.
>> It also worked on Windows XP With Python 2.7, so my best guess is that
>> this is a very especific problem that only happens with some particular
>> combination of Windows and Python version (I recall something similar in
>> an old bug).
>>
>> Could you tell me those versions?
>
> Both Windows 7 and XP, Python 2.6.6.
>
>> And if you are still being able to replicate this issue, does this patch
>> help?:
>
> I prefer to wait for you to try the above recipe and tell me if you
> can reproduce the problem. If you can't, I will try the patch.
>
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.
Regards,
Fabián
next prev parent reply other threads:[~2014-11-14 13:05 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 [this message]
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
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=87bnoahqzr.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).