Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #100606
| From | Marko Rauhamaa <marko@pacujo.net> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Should stdlib files contain 'narrow non breaking space' U+202F? |
| Date | 2015-12-19 00:16 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <8760zvjtbm.fsf@elektro.pacujo.net> (permalink) |
| References | (1 earlier) <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> <mailman.57.1450475780.30845.python-list@python.org> |
Terry Reedy <tjreedy@udel.edu>: > Guido also wants syntax chars and identifiers in stdlib code kept to > ascii only for universal readability. Readability, or writability? Most people would have no idea how to produce the characters with their keyboards. Marko
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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