➜
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.
Created on 2010-11-12 20:22 by vbr, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg121070 - (view) | Author: Vlastimil Brom (vbr) | Date: 2010-11-12 20:22 | |
I'd like to suggest updating the unicodedata module according to the recent Unicode standard 6.0 http://www.unicode.org/versions/Unicode6.0.0/ I'm sorry to bother, in case this is planned automatically, I just wasn't able to find the respective information. Would it be possible to apply such update also for the upcomming python 2.7.1, or are there some showstoppers/incompatibilities... with regard to the new unicode version? regards, vbr |
|||
| msg121071 - (view) | Author: Martin v. Löwis (loewis) *  |
Date: 2010-11-12 20:30 | |
The database had been updated already in r85371. Backporting this change to maintenance branches is not allowed by policy. |
|||
| msg121077 - (view) | Author: Vlastimil Brom (vbr) | Date: 2010-11-12 21:02 | |
Thanks for the clarification; I obviously looked in an inappropriate branch before. Sorry for the noise... vbr |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:08 | admin | set | github: 54609 |
| 2010-11-12 21:02:05 | vbr | set | messages: + msg121077 |
| 2010-11-12 20:30:00 | loewis | set | status: open -> closed nosy: + loewis messages: + msg121071 resolution: fixed |
| 2010-11-12 20:22:53 | vbr | create | |