Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <random832@fastmail.us>
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; 'root': 0.05; 'reject': 0.07; 'subject:bug': 0.07; 'accepted,': 0.09; 'arguments': 0.09; 'bug.': 0.09; 'constructor': 0.09; 'parsing': 0.09; 'received:internal': 0.09; 'python': 0.11; 'bug': 0.12; 'identifiers': 0.16; 'likewise': 0.16; 'message- id:@webmail.messagingengine.com': 0.16; 'received:10.202': 0.16; 'received:10.202.2': 0.16; 'received:10.202.2.44': 0.16; 'received:66.111': 0.16; 'received:66.111.4': 0.16; 'received:compute4.internal': 0.16; 'received:messagingengine.com': 0.16; 'wrote:': 0.18; 'code.': 0.18; 'wed,': 0.18; 'seems': 0.21; 'accepted.': 0.22; 'byte': 0.24; "shouldn't": 0.24; 'unicode': 0.24; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'apparently': 0.31; 'anyone': 0.31; 'stuff': 0.32; 'core': 0.34; "i'd": 0.34; 'received:66': 0.35; 'but': 0.35; 'subject:?': 0.36; 'should': 0.36; 'received:10': 0.37; 'being': 0.38; 'problems': 0.38; 'depends': 0.38; 'nov': 0.38; 'to:addr :python-list': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'from:no real name:2**0': 0.61; 'conversion': 0.61; 'header :Message-Id:1': 0.63; '26,': 0.68; '2014,': 0.84
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.us; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=mesmtp; bh=H9s6l8zUvCC/22AxZTt0/Zrjw4E=; b=JAuSG+ gRGNTTcFO9WAXcfy2fk889Fzl+M1qWq9v2QE0x0+Litpc16GavnWhegKtdr/R4fG FzI3qj8WoUU0b3N4nM9/e+ir2iYiRhN5BrHUXbGmIE842JdaVWlPK0Tk5ypfYGdp vefOLcoKo8gPybkyfBtP8p+7iB+kZwX7t5HYM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=H9s6l8zUvCC/22AxZTt0 /Zrjw4E=; b=m4+ek75lV0clA1/wptuezn9WpMDVdjWp0hyayxclKKoLJ0O/sNRe FyvFf00VYM8eJcNWYTBK5ZylkDaXOHVqN2GtZg1Gan8EbXQLsREqXAFuO1d5iVrx N6lI/VgNklFy1wjFa5ozzgi+mIHOT5cujUiQUNBAF4+UlivsjpwE7oc=
X-Sasl-Enc: ao1rofbeUPUc8XIvApSqHbMppfdN66paWnX14vAyBK2v 1417015925
From: random832@fastmail.us
To: python-list@python.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-53201334
Subject: Re: bug or feature in enum34 py2.7 backport?
Date: Wed, 26 Nov 2014 10:32:05 -0500
In-Reply-To: <CAPTjJmo8KbZbk4etqMqvOqrAN6p3J7cQDhdoMPTBysQWfbxOuw@mail.gmail.com>
References: <1b49aa55-ba5f-4e70-8ddb-ae5dea3a40da@googlegroups.com> <1417010748.2940071.195658861.2859C26B@webmail.messagingengine.com> <CAPTjJmo8KbZbk4etqMqvOqrAN6p3J7cQDhdoMPTBysQWfbxOuw@mail.gmail.com>
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
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>
Newsgroups: comp.lang.python
Message-ID: <mailman.16334.1417015927.18130.python-list@python.org>
Lines: 15
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1417015927 news.xs4all.nl 2915 [2001:888:2000:d::a6]:34704
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:81585

On Wed, Nov 26, 2014, at 09:40, Chris Angelico wrote:
> I'd say that's a limitation, not a bug. A lot of stuff in Python 2
> depends on identifiers being ASCII-only byte strings, including -
> apparently - parts of the core code.

But why shouldn't the type constructor do the conversion (and any
validation of being ASCII-only) when parsing the arguments? The root
cause seems to be that it parses its arguments with "SO!O!:type"
(typeobject.c, line 2097). Does anyone know what problems would be
caused, in general, by having S do a conversion if provided with a
unicode object?

It seems like if it is a bug to reject long where int is accepted, it
should be likewise considered a bug to reject ASCII-only unicode where
str is accepted.