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

Path	csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!not-for-mail
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: Should stdlib files contain 'narrow non breaking space' U+202F?
Date	Fri, 18 Dec 2015 10:18:56 +1100
Lines	36
Message-ID	<mailman.40.1450394339.30845.python-list@python.org> (permalink)
References	<n4vf3d$rer$1@ger.gmane.org>
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8
X-Trace	news.uni-berlin.de WKvCBffokw5NfdkkSHSJKwmSlw6usQ6PKxRBNtcddUlg==
Return-Path	<rosuav@gmail.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.001
X-Spam-Evidence	'H': 1.00; 'S': 0.00; 'debug': 0.04; 'cpython': 0.05; 'executable': 0.07; "subject:' ": 0.07; 'utf-8': 0.07; 'cc:addr:python-list': 0.09; 'script,': 0.09; 'subject:files': 0.09; 'python': 0.10; '2.7': 0.13; '-exec': 0.16; '-name': 0.16; '10:05': 0.16; 'ascii,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'received:209.85.213.176': 0.16; 'received:io': 0.16; 'received:psf.io': 0.16; 'subject:breaking': 0.16; 'subject:non': 0.16; 'wrote:': 0.16; 'library': 0.20; '2015': 0.20; 'cc:2**0': 0.20; 'cc:addr:python.org': 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; 'fri,': 0.27; 'message-id:@mail.gmail.com': 0.27; 'character': 0.29; "i'm": 0.30; 'code': 0.30; 'skip:. 10': 0.32; 'url:python': 0.33; 'curious': 0.33; 'file': 0.34; 'running': 0.34; 'received:google.com': 0.35; 'text': 0.35; 'skip:. 20': 0.35; 'unicode': 0.35; 'something': 0.35; 'asking': 0.35; 'but': 0.36; 'should': 0.36; 'url:org': 0.36; 'received:209.85': 0.36; 'subject:?': 0.36; 'subject:: ': 0.37; 'received:209.85.213': 0.37; 'listing': 0.38; 'received:209': 0.38; 'files': 0.38; 'why': 0.39; 'does': 0.39; 'mark': 0.40; 'your': 0.60; 'tracking': 0.61; 'minutes': 0.64; 'between': 0.65; 'chrisa': 0.84; 'subject:space': 0.84; 'url:cpython': 0.84; 'url:rev': 0.84; 'to:none': 0.91; 'comment.': 0.91; 'subject:+': 0.91
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=2Xny8XrgTPCn3455GBEFAw/Hxjk/cGUdLzsWeAXtk+A=; b=JetWcDi1TmIiIMuu70Ih9JIxCNLbT3vQGwJCyJ6VNO8u6Mt9GAdnecneFCEpX6js9B Y1h5x7Ylnq2mLLwNfGCNNv3MPGNzJ1j2f8PeH7VtKVfVVUDIl5aEYRsUt3eqt54FLZHN SKnyiiFrSPM82NF1EBMcxPJPgKCrwhqEZwMVvNV5neBIiU++1f9AQSs/hbwUhZUKywzp zkYNNUakPcwergEJ2nr9pYZv9jF4eIw4tPy+YW526Bd+KIcSZb8Wbmvxj3tkTkWc3eQi R+BPQWtsCZmKr8KoGjXD7rANMQ8JeGfX0zPfwyFDq7/dksmgvldFt402KorzQWe5smFH nJSA==
X-Received	by 10.50.82.70 with SMTP id g6mr3076igy.13.1450394336700; Thu, 17 Dec 2015 15:18:56 -0800 (PST)
In-Reply-To	<n4vf3d$rer$1@ger.gmane.org>
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:100575

Show key headers only | View raw

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:

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

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

Thread

Re: Should stdlib files contain 'narrow non breaking space' U+202F? Chris Angelico <rosuav@gmail.com> - 2015-12-18 10:18 +1100

csiph-web