Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!solaris.cc.vt.edu!news.vt.edu!newsfeed-00.mathworks.com!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Obnoxious postings from Google Groups Date: Mon, 5 Nov 2012 18:20:38 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 23 Message-ID: References: NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1352139638 8358 64.122.56.22 (5 Nov 2012 18:20:38 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Mon, 5 Nov 2012 18:20:38 +0000 (UTC) User-Agent: slrn/pre1.0.0-18 (Linux) Xref: csiph.com comp.lang.python:32777 On 2012-11-05, Dennis Lee Bieber wrote: > On Mon, 5 Nov 2012 17:39:35 +1100, Chris Angelico > declaimed the following in gmane.comp.python.general: > >> >> It's nothing to do with operating system. File names are names, and >> spaces in them are seldom worth the hassle unless you manipulate those >> files solely using a GUI. >> > At least spaces are visible. > > CP/V would accept non-printable characters in file names... Things > like BEL were valid -- but figure out where in the name the BEL > character was when listing the directory contents Don't most OSes allow non-printing characters in filenames? VMS and Unix always have. AFAIK, there are only two characters that can't appear in a Unix filename: '\x00' and '/'. -- Grant Edwards grant.b.edwards Yow! I feel better about at world problems now! gmail.com