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.

Title: Porting Extension Modules to Python 3 documentation mention about PyString_* functions in Python 3
Type: Stage: resolved
Components: Documentation Versions: Python 3.4, Python 3.5
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: benjamin.peterson, berker.peksag, docs@python, georg.brandl, python-dev
Priority: normal Keywords:

Created on 2014-10-28 04:44 by berker.peksag, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (4)
msg230119 - (view) Author: Berker Peksag (berker.peksag) * (Python committer) Date: 2014-10-28 04:44
"Porting Extension Modules to Python 3" document mention about "PyString_*" functions in Python 3. I think the correct prefix should be "PyUnicode_*".


    "Python 3’s str() (PyString_* functions in C) type is equivalent to Python 2’s unicode() (PyUnicode_*)."
msg230125 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2014-10-28 08:17
Correct, there are no PyString_ functions in 3.x.
msg230174 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2014-10-28 20:39
New changeset 9141199800fe by Georg Brandl in branch '3.4':
Closes #22748: there are no PyString C functions in 3.x.
msg230176 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2014-10-28 21:19
New changeset 18f346abdfbe by Georg Brandl in branch '2.7':
Closes #22748: there are no PyString C functions in 3.x.
Date User Action Args
2022-04-11 14:58:09adminsetgithub: 66937
2014-10-28 21:19:32python-devsetmessages: + msg230176
2014-10-28 20:39:37python-devsetstatus: open -> closed

nosy: + python-dev
messages: + msg230174

resolution: fixed
stage: needs patch -> resolved
2014-10-28 08:17:39georg.brandlsetnosy: + georg.brandl
messages: + msg230125
2014-10-28 04:44:29berker.peksagcreate