python 2.7.12 on Linux behaving differently than on Windows

Paul Moore p.f.moore at
Tue Dec 6 09:25:39 EST 2016

On Tuesday, 6 December 2016 13:25:40 UTC, BartC  wrote:
> On 06/12/2016 12:40, Gregory Ewing wrote:
> > BartC wrote:
> >> I've given a dozen examples where the shell's auto-expansion can screw
> >> things up.
> >
> > Only because you're taking Windows conventions and trying
> > to apply them to Unix.
> What, the convention of NOT assuming that any command parameter that 
> uses * or ? MUST refer to whatever set of filenames happen to match in 
> the current directory? And to then insert N arbitrary filenames in the 
> parameter list.

Correct - with the exception that it's not that it MUST - there's ways to prevent that happening, just ones that aren't the default.

> That's a pretty good convention, yes?!

Yes. It has its benefits.

> (Or should that be yesx! yesy!)

No, because the rules for text in an email are different from those for text in a shell. But you seem to be arguing that the rules should be the same everywhere, so maybe in your world, yes it should be. Most other people understand the concept of context, though.


More information about the Python-list mailing list