Make _PyUnicode_AsString as public API

[bhy]

BPO	6223
Nosy	@birkenfeld, @benjaminp

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/birkenfeld'
closed_at = <Date 2009-06-06.17:25:59.351>
created_at = <Date 2009-06-06.17:11:03.305>
labels = ['extension-modules', 'interpreter-core', 'type-feature', 'expert-unicode', 'docs']
title = 'Make _PyUnicode_AsString as public API'
updated_at = <Date 2009-06-06.17:25:59.344>
user = 'https://bugs.python.org/bhy'

bugs.python.org fields:

activity = <Date 2009-06-06.17:25:59.344>
actor = 'benjamin.peterson'
assignee = 'georg.brandl'
closed = True
closed_date = <Date 2009-06-06.17:25:59.351>
closer = 'benjamin.peterson'
components = ['Documentation', 'Extension Modules', 'Interpreter Core', 'Unicode']
creation = <Date 2009-06-06.17:11:03.305>
creator = 'bhy'
dependencies = []
files = []
hgrepos = []
issue_num = 6223
keywords = []
message_count = 2.0
messages = ['89007', '89008']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'benjamin.peterson', 'bhy']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue6223'
versions = ['Python 3.1', 'Python 3.2']

[bhy]

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!

[benjaminp]

They are not public because implicitly encoding unicode is bad practice
in Python 3. You should use PyUnicode_AsEncodedString() or such.