(original) (raw)
On Wed, Jul 18, 2012 at 3:35 PM, Eli Bendersky <eliben@gmail.com> wrote:
A more correctly formulated question would be: why is _PyBytes_Join part of the limited API, while PyUnicode_Join is in the full API. Is there a reason for the former to be less stable than the latter?
Hi,
PyUnicode\_Join is a public C API function. However, its cousin for the bytes object is tucked privately in Objects/bytesobject.c as \_PyBytes\_Join. Is there any harm in exposing it publicly?
A more correctly formulated question would be: why is _PyBytes_Join part of the limited API, while PyUnicode_Join is in the full API. Is there a reason for the former to be less stable than the latter?
Thanks in advance,
Eli