Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #100602
| X-Received | by 10.98.2.18 with SMTP id 18mr3449931pfc.11.1450454136709; Fri, 18 Dec 2015 07:55:36 -0800 (PST) |
|---|---|
| X-Received | by 10.50.78.232 with SMTP id e8mr65302igx.6.1450454136677; Fri, 18 Dec 2015 07:55:36 -0800 (PST) |
| Path | csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!mv3no13346125igc.0!news-out.google.com!l1ni7205igd.0!nntp.google.com!mv3no13346115igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail |
| Newsgroups | comp.lang.python |
| Date | Fri, 18 Dec 2015 07:55:36 -0800 (PST) |
| In-Reply-To | <5673d6ac$0$1612$c3e8da3$5496439d@news.astraweb.com> |
| Complaints-To | groups-abuse@google.com |
| Injection-Info | glegroupsg2000goo.googlegroups.com; posting-host=2a02:120b:2c76:5d70:3514:6dd0:a349:329a; posting-account=ung4FAoAAAC46zhHJ0Nsnuox7M5gDvs_ |
| NNTP-Posting-Host | 2a02:120b:2c76:5d70:3514:6dd0:a349:329a |
| 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> |
| User-Agent | G2/1.0 |
| MIME-Version | 1.0 |
| Message-ID | <bc36cf67-83c7-462b-aefa-2b9db711c523@googlegroups.com> (permalink) |
| Subject | Re: Should stdlib files contain 'narrow non breaking space' U+202F? |
| From | wxjmfauth@gmail.com |
| Injection-Date | Fri, 18 Dec 2015 15:55:36 +0000 |
| Content-Type | text/plain; charset=ISO-8859-1 |
| Content-Transfer-Encoding | quoted-printable |
| Xref | csiph.com comp.lang.python:100602 |
Show key headers only | View raw
Le vendredi 18 décembre 2015 10:49:45 UTC+1, Steven D'Aprano a écrit : > 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. > You know, Narrow-minded ascii users/code developers are narrow- minded ascii users/code developers and they will always be and stay narrow-minded ascii users/code developers. There is a very simple way to check it: There are not even able to make their product, eg Python 3.5.1, crash with an "é", U+00E9. As a Unicode lover (and a little bit more), this is what is very interesting with this language. jmf
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