➜

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.

Author berker.peksag
Recipients benjamin.peterson, berker.peksag, docs@python
Date 2014-10-28.04:44:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414471469.41.0.545994852005.issue22748@psf.upfronthosting.co.za>
In-reply-to
Content 
"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_* functions in C) type is equivalent to Python 2’s unicode() (PyUnicode_*)."
History
Date User Action Args
2014-10-28 04:44:29berker.peksagsetrecipients: + berker.peksag, benjamin.peterson, docs@python
2014-10-28 04:44:29berker.peksagsetmessageid: <1414471469.41.0.545994852005.issue22748@psf.upfronthosting.co.za>
2014-10-28 04:44:29berker.peksaglinkissue22748 messages
2014-10-28 04:44:28berker.peksagcreate