[ python-Feature Requests-1031288 ] Update unicodedata to version 4.0.1

[SourceForge.net]

Feature Requests item #1031288, was opened at 2004-09-20 15:37
Message generated for change (Comment added) made by gbrandl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1031288&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Unicode
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Oliver Horn (ohorn)
Assigned to: Nobody/Anonymous (nobody)
Summary: Update unicodedata to version 4.0.1

Initial Comment:
The unicodedata library (shipped with Python 2.3.4 and
2.4a3) is still version 3.2.0 albeit version 4.0.1 is
available from unicode.org.
Is it possible to update 4.0.1, at least for Python 2.4?


----------------------------------------------------------------------

>Comment By: Georg Brandl (gbrandl)
Date: 2006-08-10 20:40

Message:
Logged In: YES 
user_id=849994

unicodedata was updated to 4.1.0 for 2.5 while retaining
3.2.0 available.

----------------------------------------------------------------------

Comment By: M.-A. Lemburg (lemburg)
Date: 2004-10-25 08:50

Message:
Logged In: YES 
user_id=38388

While Python 2.4 is not possible anymore, we should consider
this change for Python 2.5.

I don't think we should stick to
version 3.2 forever just because some RFC editors got 
their text wrong. Besides, changes to the Unicode database
are usually backwards compatible for the vast majority of
code points.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2004-10-23 11:54

Message:
Logged In: YES 
user_id=21627

For Python 2.4, this is not possible, as the beta has
already been published.

For Python 2.5, it might be possible, but is difficult.
Python relies on the unicodedata 3.2.0, as the IDNA RFCs
mandate that Unicode 3.2 is used to implement IDNA. So any
integration of 4.0.1 must
a) still maintain access to the 3.2.0 data
b) change all code that relies on 3.2.0 data to refer to
these data explicitly
c) not simply double the amount of data, but somehow allow
for a differential representation.

This is very difficult to implement, and hence hasn't been
implemented for 2.4 (and might not be implemented for 2.5).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1031288&group_id=5470