python 2.7.12 on Linux behaving differently than on Windows

Marko Rauhamaa marko at pacujo.net
Thu Dec 8 18:03:48 EST 2016


Gregory Ewing <greg.ewing at canterbury.ac.nz>:

> Grant Edwards wrote:
>> But _paths_ can, and Windows command-line apps and shells choke on
>> paths when written with "/" separators because way-back when the
>> MS-DOS "designers" decided to use "/" as the default option
>> character.
>
> To be fair to them, the use of "/" for options can be traced back to
> earlier systems such as CP/M and RT-11, which didn't even have
> hierarchial file systems, so choice of path separators wasn't an
> issue.

I find it a bit annoying that "/" cannot be used in Linux filenames.
Slashes have very common everyday uses and it's a pity they are
reserved. Instead, ASCII control characters are allowed, which is of no
use.

And the Linux example of the other day is just terrible. Globs can do
surprising damage if filenames should start with a minus sign.

The naive command:

    cp *.c backup/

should really be:

    cp ./*.c backup/

or:

    cp -- *.c backup/

but who does that?


Marko


More information about the Python-list mailing list