Obnoxious postings from Google Groups
ramit.prasad at jpmorgan.com
Tue Nov 6 17:52:03 CET 2012
Grant Edwards wrote:
> On 2012-11-05, Roy Smith <roy at panix.com> wrote:
> > In article <mailman.3269.1352097585.27098.python-list at python.org>,
> > Chris Angelico <rosuav at gmail.com> wrote:
> >> 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.
> > That's a very ascii-esqe attitude. In a fully unicode world, I could
> > easily see using U+00A0 (NO-BREAK SPACE) in file names, and still have
> > space-delimited CLI work just fine.
> No, it wouldn't work just fine. You'd never know when looking at
> names whether it was a "regular" space or a "no-break space", and
> names would be visually ambiguous. Visually ambiguous names are
Not to mention that in the GUI I (usually) want the space to be a
> > But, yeah, in the world we live in today, I try to avoid spaces in
> > filenames. But, instead of turning "My File Name" into MyFileName, I'll
> > usually do it as My-File-Name or My_File_Name.
This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.
More information about the Python-list