python 2.7.12 on Linux behaving differently than on Windows

Nathan Ernst nathan.ernst at
Mon Dec 5 21:42:19 EST 2016

Rather than argue about what is/should be allowed by a filesystem, this
defines what is allowed on NTFS (default for modern Windows systems):

One can complain about whether or not something should be allowed, but,
you'd have to take that up with Microsoft (and I'll doubt you'll make a
convincing enough argument for them to change it).

What is allowed on linux may be defined by linux itself, and it may be
restricted by the filesystem type itself (I don't know).


On Mon, Dec 5, 2016 at 8:25 PM, Dennis Lee Bieber <wlfraed at>

> On Mon, 5 Dec 2016 20:55:41 +0000, BartC <bc at> declaimed the
> following:
> >This was a response to someone saying the wildcard param needs to be at
> >the end. There need be no such restriction if handled properly (ie. no
> >auto-expansion).
> >
>         That only applies if there is no prefix indicating a command option
> from a file name.
> >but one of the files in the list is called "-lm", or some other option
>         -lm is not a valid file name on the OS's that use - as an option
> prefix.
> >Without expansion, input is easy to parse: filespec, followed by
> >optional options. But with expansion, now you have to decide if a
> >particular argument is an option, or a filename.
> >
>         And you do that using a delimiter character that is not valid in
> filenames. On Windows, file names can not have a /, and that is the
> character used by the command line interpreter to indicate an option
> follows. On UNIX, - is used as the delimiter of an option.
> --
>         Wulfraed                 Dennis Lee Bieber         AF6VN
>     wlfraed at    HTTP://
> --

More information about the Python-list mailing list