Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #100605

Re: Should stdlib files contain 'narrow non breaking space' U+202F?

From Terry Reedy <tjreedy@udel.edu>
Newsgroups comp.lang.python
Subject Re: Should stdlib files contain 'narrow non breaking space' U+202F?
Date 2015-12-18 16:56 -0500
Message-ID <mailman.57.1450475780.30845.python-list@python.org> (permalink)
References <n4vf3d$rer$1@ger.gmane.org> <CAPTjJmoa5dBiDJ5zDu4jEy4MjOm6vp=J3zLqJw7ZfEUf9da=DQ@mail.gmail.com> <n509h0$p6h$1@ger.gmane.org> <mailman.45.1450421501.30845.python-list@python.org> <5673d6ac$0$1612$c3e8da3$5496439d@news.astraweb.com>

Show all headers | View raw


On 12/18/2015 4:49 AM, Steven D'Aprano wrote:
> On Fri, 18 Dec 2015 05:51 pm, Chris Angelico wrote:
>
>> I would be inclined to ASCIIfy the apostrophes, dashes, and the
>> connection.py space that started this thread. People's names, URLs,
>> and demonstrative characters I'm more inclined to leave. Agreed?
>
> No.

No in the sense of a blanket rule.  But in at least some cases, yes.  In 
idlelib/README.txt, ' somehow got changed to the a latin-1 encoded 
slanted apostrophe (by Notepad++ I think) when I edited the file.  Since 
IDLE *assumes* that the file is ascii-only and does not specify an 
encoding, display failed on Serhiy's non-Windows system.  Issue 25905. 
I changed it back. Other accidents should be fixed.

Guido also wants syntax chars and identifiers in stdlib code kept to 
ascii only for universal readability.  Maybe that will change someday.

-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Should stdlib files contain 'narrow non breaking space' U+202F? Chris Angelico <rosuav@gmail.com> - 2015-12-18 17:51 +1100
  Re: Should stdlib files contain 'narrow non breaking space' U+202F? Steven D'Aprano <steve@pearwood.info> - 2015-12-18 20:49 +1100
    Re: Should stdlib files contain 'narrow non breaking space' U+202F? wxjmfauth@gmail.com - 2015-12-18 07:55 -0800
    Re: Should stdlib files contain 'narrow non breaking space' U+202F? Terry Reedy <tjreedy@udel.edu> - 2015-12-18 16:56 -0500
      Re: Should stdlib files contain 'narrow non breaking space' U+202F? Marko Rauhamaa <marko@pacujo.net> - 2015-12-19 00:16 +0200
        Re: Should stdlib files contain 'narrow non breaking space' U+202F? Chris Angelico <rosuav@gmail.com> - 2015-12-19 10:58 +1100
      Re: Should stdlib files contain 'narrow non breaking space' U+202F? wxjmfauth@gmail.com - 2015-12-19 00:52 -0800

csiph-web