sys.argv and quoted arguments on command line

[fcr]

BPO	10322
Nosy	@ericvsmith, @bitdancer
Files	argtest: test program to reproduce problem

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2010-11-05.13:09:25.402>
created_at = <Date 2010-11-05.10:06:34.111>
labels = ['type-bug', 'invalid']
title = 'sys.argv and quoted arguments on command line'
updated_at = <Date 2010-11-05.13:11:26.935>
user = 'https://bugs.python.org/fcr'

bugs.python.org fields:

activity = <Date 2010-11-05.13:11:26.935>
actor = 'eric.smith'
assignee = 'none'
closed = True
closed_date = <Date 2010-11-05.13:09:25.402>
closer = 'fcr'
components = []
creation = <Date 2010-11-05.10:06:34.111>
creator = 'fcr'
dependencies = []
files = ['19503']
hgrepos = []
issue_num = 10322
keywords = []
message_count = 6.0
messages = ['120480', '120484', '120486', '120487', '120488', '120491']
nosy_count = 3.0
nosy_names = ['eric.smith', 'r.david.murray', 'fcr']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10322'
versions = ['Python 2.5', 'Python 3.1']

[fcr]

Words in quoted command line arguments containing whitespace are split into separate entries of the argument vector sys.argv. This implemetation (quote removal + word splitting) removes information required to read string arguments passed via the command line.

The expected behaviour would be to unquote the argument, but not to conduct word splitting within the quoted text.

----
Test program output:

./argtest arg1 arg2 "this should be a single argument"

['./argtest', 'arg1', 'arg2', 'this', 'should', 'be', 'a', 'single', 'argument']
----

(observed with Python 3.1.2 (r312:79147, Oct 28 2010, 14:12:33)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2

[ericvsmith]

I don't see this behavior on MacOS:

$ ./argtest arg1 arg2 "this should be a single argument"
2.6.1 (r261:67515, Feb 11 2010, 15:47:53) 
[GCC 4.2.1 (Apple Inc. build 5646)]
['./argtest', 'arg1', 'arg2', 'this should be a single argument']

This splitting is done by the shell (Unix-like systems) or by the C runtime (Windows), not by Python. What OS are you running?

[fcr]

2.6.18-194.17.1.el5 #1 SMP Wed Sep 29 12:51:33 EDT 2010 i686 i686 i386 GNU/Linux

GNU bash, version 3.2.25(1)-release (i686-redhat-linux-gnu)

I wrote test program in C to do the same thing as before and the arguments are treated properly:

./testcargs arg1 arg2 "this should be one arg"
argument 0 is: ./testcargs
argument 1 is: arg1
argument 2 is: arg2
argument 3 is: this should be one arg

My suspicion is that sys implementation goes into a branch intended for a different OS.

[ericvsmith]

The python version works for me also on a Fedora box with 3.2 and 2.7.

What shell are you using?

Did you compile this python yourself, or did it come with your distro?

[bitdancer]

Works fine for me on Gentoo linux.

What exactly is 'python' in your path, and what happens if you do /usr/bin/python3 argtest?

I'm 99.99% certain this is not a bug in Python, otherwise it would have been reported long before now, since it would represent a major change in behavior.

[fcr]

You are right, it seems to work when the file is passed directly into python so the quotes are stripped somewhere before python even gets to see them.

Thanks