On Wed, Jul 18, 2012 at 3:35 PM, Eli Bendersky <eliben at gmail.com> wrote: > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120718/bbd1ac3a/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4