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 bhy
Recipients bhy, georg.brandl
Date 2009-06-06.17:11:02
SpamBayes Score 2.6235202e-05
Marked as misclassified No
Message-id <1244308265.08.0.506507735575.issue6223@psf.upfronthosting.co.za>
In-reply-to
Content
Why _PyUnicode_AsString and _PyUnicode_AsStringAndSize are not public
API? They are very useful when porting extension module to Python 3,
because they have the semantic as same as PyString_AsString. For
extension author, these API can be used for replacing PyString_AsString
without any other change in code logic.

So why not make these API public? Any consideration? If we can document
these API, then C extension author can know them and use them, without
spending a lot of time to dig them out from Python source code.

Thanks!
History
Date User Action Args
2009-06-06 17:11:05bhysetrecipients: + bhy, georg.brandl
2009-06-06 17:11:05bhysetmessageid: <1244308265.08.0.506507735575.issue6223@psf.upfronthosting.co.za>
2009-06-06 17:11:03bhylinkissue6223 messages
2009-06-06 17:11:02bhycreate