[issue22748] Porting Extension Modules to Python 3 documentation mention about PyString_* functions in Python 3

2014-10-28 Thread Georg Brandl
Georg Brandl added the comment: Correct, there are no PyString_ functions in 3.x. -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22748 ___

[issue22748] Porting Extension Modules to Python 3 documentation mention about PyString_* functions in Python 3

2014-10-28 Thread Roundup Robot
Roundup Robot added the comment: New changeset 9141199800fe by Georg Brandl in branch '3.4': Closes #22748: there are no PyString C functions in 3.x. https://hg.python.org/cpython/rev/9141199800fe -- nosy: +python-dev resolution: - fixed stage: needs patch - resolved status: open -

[issue22748] Porting Extension Modules to Python 3 documentation mention about PyString_* functions in Python 3

2014-10-28 Thread Roundup Robot
Roundup Robot added the comment: New changeset 18f346abdfbe by Georg Brandl in branch '2.7': Closes #22748: there are no PyString C functions in 3.x. https://hg.python.org/cpython/rev/18f346abdfbe -- ___ Python tracker rep...@bugs.python.org

[issue22748] Porting Extension Modules to Python 3 documentation mention about PyString_* functions in Python 3

2014-10-27 Thread Berker Peksag
New submission from Berker Peksag: Porting Extension Modules to Python 3 document mention about PyString_* functions in Python 3. I think the correct prefix should be PyUnicode_*. From https://docs.python.org/3/howto/cporting.html#str-unicode-unification: Python 3’s str() (PyString_*