<div dir="ltr"><div class="gmail_quote">On Wed, Jul 18, 2012 at 3:35 PM, Eli Bendersky <span dir="ltr"><<a href="mailto:eliben@gmail.com" target="_blank">eliben@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,<br><br>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?<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></div></blockquote><div><br>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?<br>
<br>Thanks in advance,<br>Eli<br><br></div></div><br></div>