This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, ezio.melotti, lemburg, loewis
Date 2010-11-29.19:04:54
SpamBayes Score 4.996e-16
Marked as misclassified No
Message-id <AANLkTi=SbWju7mAuCekMrA5uk5ey9YFQGYmv129eMGd1@mail.gmail.com>
In-reply-to <4CF3F0EA.3090308@egenix.com>
Content
On Mon, Nov 29, 2010 at 1:29 PM, Marc-Andre Lemburg
<report@bugs.python.org> wrote:
..
>
> I consider this a bug (which is why I added Python 2.7 to the list
> of versions), since those code points need to be mapped to decimal
> and digit as well (see the references I posted; and compare ).
>

I don't disagree.  However using Unicode 5.2.0 instead of the latest
6.0.0 may be considered a bug as well.  The practical issue is whether
to maintain two separate versions of Tools/unicode for 3.x and 2.7 or
merge 3.x changes back to 2.7 and support 3.x using 2to3.  Another
option is to simply use only 2.7 (or only 3.x) with Tools/unicode and
maintain control the differences between 2.7 and 3.x using a command
line switch.
History
Date User Action Args
2010-11-29 19:04:56belopolskysetrecipients: + belopolsky, lemburg, loewis, ezio.melotti
2010-11-29 19:04:54belopolskylinkissue10575 messages
2010-11-29 19:04:54belopolskycreate