Change by Jonny Li :
Added file: https://bugs.python.org/file49189/Screen Shot 2020-05-24 at
10.56.10.png
___
Python tracker
<https://bugs.python.org/issue40
Change by Jonny Li :
--
assignee: terry.reedy
components: IDLE
files: Screen Shot 2020-05-24 at 10.56.55.png
nosy: Jonny Li, terry.reedy
priority: normal
severity: normal
status: open
title: command 'elif' does not work
type: compile error
versions: Python 3.8
Added f
Jonny Weese added the comment:
> So the command_string provided (the first word or the first quoted
> expression) is interpreted as a shell program, and this program is invoked
> with the remaining words as its arguments.
Correct.
> As you say, simply slapping quotes around
Jonny Weese added the comment:
> it seems strange/wrong to invoke an executable via "bash -c executable arg1
> arg2", rather than just "executable arg1 arg2"!
I agree it's strange to invoke a single executable that way, but remember that
-c allows a string o
Jonny Weese added the comment:
I believe this behavior is expected (at least in posix-land).
Lib/subprocess.py L1702 shows that whenever shell=True, the args that are
constructed are [unix_shell, "-c"] + args.
And so we can reproduce your behavior just using a regular shell
New submission from Jonny Fuller :
Hi friends,
I noticed strange behavior involving unittest discovery with namespace
packages. Using dot notation to discover test packages within a namespace
package will fail, but will succeed when using path notation.
It feels awkward that dot path would
New submission from jonny:
I am running debian stretch on 64bit arm system. I am trying to install python
3.6.2. But facing errors in these tests while running make test.
I have installed these libraries :: apt install liblzma-dev libz-dev
libreadline-dev libncursesw5-dev libssl-dev libgdbm
