➜
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 2004-03-31 00:51 by hyeshik.chang, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| unichrwide.diff | hyeshik.chang, 2004-03-31 00:56 | a patch that enables unichr(wide) | ||
| Messages (3) | |||
|---|---|---|---|
| msg45694 - (view) | Author: Hyeshik Chang (hyeshik.chang) *  |
Date: 2004-03-31 00:51 | |
PyUnicode_FromOrdinal has code supporting UCS2 build already. But it is disabled by range validating routine. I think it should be either removed or modified to allow wide characters. (Please see the attachment.) |
|||
| msg45695 - (view) | Author: Martin v. Löwis (loewis) * |
Date: 2004-03-31 18:52 | |
Logged In: YES user_id=21627 PEP 261 specifies that unichr() should raise a ValueError on narrow builds, so this check must stay the way it is. If you want to make it consistent, please remove the useless support for UTF-16 instead. |
|||
| msg45696 - (view) | Author: Hyeshik Chang (hyeshik.chang) * |
Date: 2004-04-06 07:38 | |
Logged In: YES user_id=55188 Removed the code in Objects/unicodeobject.c 2.211 Thanks! |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:03 | admin | set | github: 40105 |
| 2004-03-31 00:51:17 | hyeshik.chang | create | |