python 2.7.12 on Linux behaving differently than on Windows

BartC bc at freeuk.com
Tue Dec 6 06:21:20 EST 2016


On 06/12/2016 07:37, Larry Hudson wrote:

> Now you're suggesting the _shell_ is going to read and process a CVS
> file???

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. But they can't because in 
the in-line example, parameters could be expanded. And there seems to be 
no way of turning that off, without changing the input (eg. quotes 
around parameters).

>> Shell command line processing shouldn't be attempting anything more
>> than that.
>>
> I get awfully tired of your constant pontificating about your opinions.

Opinions based on facts: I've given a dozen examples where the shell's 
auto-expansion can screw things up. And I can easily come up with more, 
as have others in the thread.

People's attitudes seem to be 'So don't that'. Or, 'So what?'.

Which suggests there is an actual problem that is being brushed under 
the carpet.

> I know they're _VERY_ strongly held beliefs on your part, but...  they
> are ONE person's opinions and are no more than opinions and they ain't
> gonna change nothin', no how, no way, not ever.

No they're not. But the auto-expansion of parameters by default is still 
wrong.

> [Sorry, I'm in a bad mood today and just had to let off a little steam...]

People spout off about Windows ALL the time. 'So what?'

-- 
Bartc




More information about the Python-list mailing list