On Tue, Dec 6, 2016 at 6:24 AM, BartC <b...@freeuk.com> wrote: >> If it sees "*", it will try to open a file named "*". > > > And people still say that the way Windows works is crazy! > > That's a valid >> >> filename in Unix, but it should be avoided. > > > No, it should be prohibited, if the file API and/or shell assign special > significance to it. >
That implies that the file system, file API, and shell are all bound together. You have to forbid in file names *any* character that has *any* significance to *any* shell. That means no quotes, no asterisks or question marks, no square brackets, no braces, etc, etc, etc..... or, alternatively, restrict your shells to all perform the exact same expansion - or no expansion at all, and then restrict all your _applications_ to perform the same expansion. Good luck. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
