old UnicodeData.txt

[doko42]

BPO	646408
Nosy	@malemburg, @loewis, @doko42

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/malemburg'
closed_at = <Date 2002-12-06.10:58:08.000>
created_at = <Date 2002-12-01.12:54:56.000>
labels = ['expert-unicode']
title = 'old UnicodeData.txt'
updated_at = <Date 2002-12-06.10:58:08.000>
user = 'https://github.com/doko42'

bugs.python.org fields:

activity = <Date 2002-12-06.10:58:08.000>
actor = 'loewis'
assignee = 'lemburg'
closed = True
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2002-12-01.12:54:56.000>
creator = 'doko'
dependencies = []
files = []
hgrepos = []
issue_num = 646408
keywords = []
message_count = 5.0
messages = ['13499', '13500', '13501', '13502', '13503']
nosy_count = 4.0
nosy_names = ['lemburg', 'loewis', 'effbot', 'doko']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue646408'
versions = ['Python 2.3']

[doko42]

[submitted at http://bugs.debian.org/171061]

The version mentioned is CVS 021121 HEAD

unicodedata.so is obviously built with older
UnicodeData.txt file,
and does not match new characters introduced in Unicode
3.2.
To fix it, I copied UnicodeData.txt (conveniently
provided by perl-modules
in /usr/share/perl/5.8.0/unicore/UnicodeData.txt) to
the top of
unpacked python2.3 source package, renamed it to
UnicodeData-Latest.txt,
ran "python Tools/unicode/makeunicodedata.py" and then
recompiled
python2.3 package. This should probably be addressed
upstream as well.

before:
>>> import unicodedata
>>> unicodedata.name(u'\u20b0')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  ValueError: no such name

after:
>>> import unicodedata
>>> unicodedata.name(u'\u20b0')
'GERMAN PENNY SIGN'

[effbot]

Logged In: YES
user_id=38376

Why is Debian shipping a "python2.3", when
Python 2.3 hasn't been released yet (it's not
even in alpha)?

(the Unicode database in the current Python
CVS has already been updated...)

</F>

[loewis]

Logged In: YES
user_id=21627

Are you sure you are using the current CVS? In my copy of
the CVS, renaming to UnicodeData-Latest is not necessary,
and GERMANY PENNY SIGN is included in the database.

To verify that you use the current CVS, please report the
value of unicodedata.unidata_version.

Fredrik, Debian has the Python 2.3 package only in
its "unstable" (and "testing") distribution, see

http://packages.debian.org/unstable/interpreters/python2.3.ht
ml

It is common to provide Debian packages for CVS versions of
software in "unstable", so that the Debian developers can
analyse effects of upcoming versions on their software.

[doko42]

Logged In: YES
user_id=60903

The CVS version (as mentioned) was 021121 HEAD. Closing the
report, as this has changed six days ago.

Frederik: Debian currently has 1.5, 2.1, 2.2 and 2.3, 2.1
beeing the default in the released (stable) distribution,
and 2.2 the default in the "unstable" distribution. I did
put 2.3 in unstable to ease building third party modules
using the new version.

[loewis]

Logged In: YES
user_id=21627

It may not matter anymore, but...

In the Debian package 2.2.94-1exp1, the changelog indicates
that it was from CVS 021120. In that version, GERMANY PENNY
SIGN is already in the Unicode database.