Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #100579
| Path | csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail |
|---|---|
| From | Terry Reedy <tjreedy@udel.edu> |
| Newsgroups | comp.lang.python |
| Subject | Re: Should stdlib files contain 'narrow non breaking space' U+202F? |
| Date | Fri, 18 Dec 2015 01:36:12 -0500 |
| Lines | 50 |
| Message-ID | <mailman.43.1450420600.30845.python-list@python.org> (permalink) |
| References | <n4vf3d$rer$1@ger.gmane.org> <CAPTjJmoa5dBiDJ5zDu4jEy4MjOm6vp=J3zLqJw7ZfEUf9da=DQ@mail.gmail.com> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=utf-8; format=flowed |
| Content-Transfer-Encoding | 7bit |
| X-Trace | news.uni-berlin.de cynNU8tpwSSWaCEXl/0JpgcSzygOgP6UEV86JfTUs11g== |
| Return-Path | <python-python-list@m.gmane.org> |
| X-Original-To | python-list@python.org |
| Delivered-To | python-list@mail.python.org |
| X-Spam-Status | OK 0.000 |
| X-Spam-Evidence | '*H*': 1.00; '*S*': 0.00; 'debug': 0.04; 'cpython': 0.05; 'guido': 0.05; 'executable': 0.07; "subject:' ": 0.07; 'utf-8': 0.07; 'non-ascii': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'script,': 0.09; 'subject:files': 0.09; 'python': 0.10; 'jan': 0.11; '2.7': 0.13; '-exec': 0.16; '-name': 0.16; '10:05': 0.16; 'ascii,': 0.16; 'invisible': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'reedy': 0.16; 'subject:breaking': 0.16; 'subject:non': 0.16; 'wrote:': 0.16; 'fixed.': 0.18; 'library': 0.20; '2015': 0.20; '3.2': 0.22; "aren't": 0.22; 'lawrence': 0.22; 'am,': 0.23; 'dec': 0.23; 'header:In-Reply-To:1': 0.24; 'url:bugs': 0.24; "i've": 0.25; 'header:User-Agent:1': 0.26; 'header:X-Complaints-To:1': 0.26; 'chris': 0.26; 'fri,': 0.27; 'cases.': 0.29; 'character': 0.29; "i'm": 0.30; 'code': 0.30; 'especially': 0.32; 'possibly': 0.32; 'skip:. 10': 0.32; 'url:python': 0.33; 'curious': 0.33; 'file': 0.34; 'running': 0.34; 'text': 0.35; 'skip:. 20': 0.35; 'unicode': 0.35; 'something': 0.35; 'asking': 0.35; 'but': 0.36; 'should': 0.36; 'there': 0.36; 'url:org': 0.36; '(and': 0.36; 'received:71': 0.36; 'to:addr:python-list': 0.36; 'subject:?': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'received:org': 0.37; 'wanted': 0.37; 'listing': 0.38; 'files': 0.38; 'why': 0.39; 'does': 0.39; 'to:addr:python.org': 0.40; 'mark': 0.40; 'still': 0.40; 'space': 0.40; 'your': 0.60; 'tracking': 0.61; 'minutes': 0.64; 'between': 0.65; 'special': 0.73; 'chrisa': 0.84; 'subject:space': 0.84; 'url:cpython': 0.84; 'url:rev': 0.84; 'comment.': 0.91; 'received:fios.verizon.net': 0.91; 'subject:+': 0.91 |
| X-Injected-Via-Gmane | http://gmane.org/ |
| X-Gmane-NNTP-Posting-Host | pool-71-185-227-36.phlapa.fios.verizon.net |
| User-Agent | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
| In-Reply-To | <CAPTjJmoa5dBiDJ5zDu4jEy4MjOm6vp=J3zLqJw7ZfEUf9da=DQ@mail.gmail.com> |
| X-BeenThere | python-list@python.org |
| X-Mailman-Version | 2.1.20+ |
| Precedence | list |
| List-Id | General discussion list for the Python programming language <python-list.python.org> |
| List-Unsubscribe | <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe> |
| List-Archive | <http://mail.python.org/pipermail/python-list/> |
| List-Post | <mailto:python-list@python.org> |
| List-Help | <mailto:python-list-request@python.org?subject=help> |
| List-Subscribe | <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> |
| Xref | csiph.com comp.lang.python:100579 |
Show key headers only | View raw
On 12/17/2015 6:18 PM, Chris Angelico wrote:
> On Fri, Dec 18, 2015 at 10:05 AM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
>> The culprit character is hidden between "Issue #" and "20540" at line 400 of
>> C:\Python35\Lib\multiprocessing\connection.py.
>> https://bugs.python.org/issue20540 and
>> https://hg.python.org/cpython/rev/125c24f47f3c refers.
>>
>> I'm asking as I've just spent 30 minutes tracking down why my debug code
>> would bomb when running on 3.5, but not 2.7 or 3.2 through 3.4.
>
> I'm curious as to why this character should bomb your code at all -
> it's in a comment. Is it that your program was expecting ASCII, or is
> it something about that particular character?
>
> Here's a quick listing of the CPython standard library files that aren't ASCII:
Last I knew, Guido still wanted stdlib files to be all-ascii, especially
possibly in special cases. There is no good reason I can think of for
there to be an invisible non-ascii space in a comment. It strikes me as
most likely an accident (typo) that should be fixed. I suspect the same
of most of the following. Perhaps you should file an issue (and patch?)
on the tracker.
> rosuav@sikorsky:~/cpython/Lib$ find -name \*.py -not -wholename
> \*test\* -exec file {} \;|grep UTF-8
> ./encodings/punycode.py: Python script, UTF-8 Unicode text executable
> ./encodings/koi8_t.py: Python script, UTF-8 Unicode text executable
> ./msilib/__init__.py: Python script, UTF-8 Unicode text executable
> ./shlex.py: Python script, UTF-8 Unicode text executable
> ./http/client.py: Python script, UTF-8 Unicode text executable
> ./distutils/command/bdist_msi.py: Python script, UTF-8 Unicode text executable
> ./multiprocessing/connection.py: Python script, UTF-8 Unicode text executable
> ./functools.py: Python script, UTF-8 Unicode text executable
> ./heapq.py: Python script, UTF-8 Unicode text executable
> ./email/message.py: Python script, UTF-8 Unicode text executable
> ./getopt.py: Python script, UTF-8 Unicode text executable
> ./urllib/request.py: Python script, UTF-8 Unicode text executable
> ./sre_compile.py: Python script, UTF-8 Unicode text executable
> ./sqlite3/dbapi2.py: Python script, UTF-8 Unicode text executable
> ./sqlite3/__init__.py: Python script, UTF-8 Unicode text executable
>
> Does your program bomb on any of these?
>
> ChrisA
>
--
Terry Jan Reedy
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Should stdlib files contain 'narrow non breaking space' U+202F? Terry Reedy <tjreedy@udel.edu> - 2015-12-18 01:36 -0500
csiph-web