python 2.7.12 on Linux behaving differently than on Windows

Chris Angelico rosuav at
Tue Dec 6 06:42:25 EST 2016

On Tue, Dec 6, 2016 at 10:21 PM, BartC <bc at> wrote:
> What follows a shell command is a set of values a,b,c,d,e. What is
> encountered in a CSV is a set of values a,b,c,d,e. You really can't see the
> similarity?
> Suppose instead of:
>   command a b c d e
> The interface was changed to be more interactive:
>   command
>   Input:  a b c d e
> So parameters are not entered on the command line, but are prompted for. Do
> you think entering a b c d e here should give exactly the same results as
> doing so on the command line?
> As far as any user is concerned, they should.

Here are two Python statements:

x = 1, 2, 3, 4, 5

f(1, 2, 3, 4, 5)

As far as any user is concerned, these should do the exact same thing.
After all, they both have five numbers separated by commas. There's
absolutely no reason for them to do anything different. And it should
be exactly the same if you write it like this:


and type "1, 2, 3, 4, 5" at the prompt. Right?

Why do you continue to claim that shells should do no parsing, yet
expect parsing to happen elsewhere? Why are shells somehow different?


More information about the Python-list mailing list