[issue9889] PyUnicode_FormatV and Py_UNICODE*?

2013-10-13 Thread Georg Brandl
Changes by Georg Brandl ge...@python.org: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9889 ___ ___ Python-bugs-list

[issue9889] PyUnicode_FormatV and Py_UNICODE*?

2013-01-15 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: The Py_UNICODE* representation is deprecated since 3.3. New features can be added only to 3.4. -- nosy: +serhiy.storchaka resolution: - rejected status: open - pending ___ Python tracker rep...@bugs.python.org

[issue9889] PyUnicode_FormatV and Py_UNICODE*?

2010-09-24 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9889 ___ ___ Python-bugs-list

[issue9889] PyUnicode_FormatV and Py_UNICODE*?

2010-09-17 Thread Michael Kleehammer
New submission from Michael Kleehammer mich...@kleehammer.com: 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

[issue9889] PyUnicode_FormatV and Py_UNICODE*?

2010-09-17 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9889 ___ ___ Python-bugs-list