Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #100587 > unrolled thread
| Started by | Serhiy Storchaka <storchaka@gmail.com> |
|---|---|
| First post | 2015-12-18 10:33 +0200 |
| Last post | 2015-12-18 07:01 -0800 |
| Articles | 2 — 2 participants |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Should stdlib files contain 'narrow non breaking space' U+202F? Serhiy Storchaka <storchaka@gmail.com> - 2015-12-18 10:33 +0200
Re: Should stdlib files contain 'narrow non breaking space' U+202F? wxjmfauth@gmail.com - 2015-12-18 07:01 -0800
| From | Serhiy Storchaka <storchaka@gmail.com> |
|---|---|
| Date | 2015-12-18 10:33 +0200 |
| Subject | Re: Should stdlib files contain 'narrow non breaking space' U+202F? |
| Message-ID | <mailman.50.1450427677.30845.python-list@python.org> |
On 18.12.15 09:43, Chris Angelico wrote: > On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka <storchaka@gmail.com> wrote: >> Agreed. Please open an issue. >> >> Using non-ASCII apostrophes and like in docstrings may be considered a bug. > > http://bugs.python.org/issue25899 Thanks. > Also noticed this. Is this a markup error? > > Lib/urllib/request.py:190: > Note that *None& may be returned if no handler handles the request (though > the default installed global OpenerDirector uses UnknownHandler to ensure > this never happens). Looks as just a typo.
[toc] | [next] | [standalone]
| From | wxjmfauth@gmail.com |
|---|---|
| Date | 2015-12-18 07:01 -0800 |
| Message-ID | <6e41601a-8086-4421-a1fb-6c3695d146dd@googlegroups.com> |
| In reply to | #100587 |
Le vendredi 18 décembre 2015 09:34:52 UTC+1, Serhiy Storchaka a écrit : > On 18.12.15 09:43, Chris Angelico wrote: > > On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka <storchaka@gmail.com> wrote: > >> Agreed. Please open an issue. > >> > >> Using non-ASCII apostrophes and like in docstrings may be considered a bug. > > > > http://bugs.python.org/issue25899 > > Thanks. > The cause of the problem is not the apostrophe, Windows, iso-8859-1, utf-8, cp1252 or ... . The cause of the problem is that the character encoding model in Python is wrong by design. This story is only reflecting it. jmf
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web