Issue 9889: PyUnicode_FormatV and Py_UNICODE*? (original) (raw)
Issue9889
Created on 2010-09-17 19:32 by mkleehammer, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (2) | ||
|---|---|---|
| msg116714 - (view) | Author: Michael Kleehammer (mkleehammer) * | Date: 2010-09-17 19:32 |
| Using Py_UNICODE* in Python 3 C extensions is significantly more cumbersome than using char* was in Python 2.x. One addition that could help would be a Py_UNICODE* format type for PyUnicode_FormatV. Many printf libraries us %S for wchar_t which would have been nicely analogous, but that is already taken for str(obj). | ||
| msg180044 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) *  |
Date: 2013-01-15 19:32 |
| The Py_UNICODE* representation is deprecated since 3.3. New features can be added only to 3.4. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:06 | admin | set | github: 54098 |
| 2013-10-13 18:24:58 | georg.brandl | set | status: pending -> closed |
| 2013-01-15 19:32:39 | serhiy.storchaka | set | status: open -> pendingnosy: + serhiy.storchakamessages: + resolution: rejected |
| 2010-09-24 20:42:04 | terry.reedy | set | versions: - Python 3.1 |
| 2010-09-17 20:10:35 | r.david.murray | set | nosy: + vstinner |
| 2010-09-17 19:32:09 | mkleehammer | create |