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 belopolsky
Recipients belopolsky, daniel.urban, eric.araujo, georg.brandl, lemburg, rhettinger, stribb, terry.reedy, thomaslee
Date 2010-11-19.15:23:07
SpamBayes Score 1.57391e-10
Marked as misclassified No
Message-id <1290180189.3.0.982102818074.issue4113@psf.upfronthosting.co.za>
In-reply-to
Content
There is an ongoing discussion about deprecating undocumented PyUnicode_AppendAndDel(). See Marc-Andre's comment in msg121371:

"""
+.. c:function:: void PyUnicode_Append(PyObject **pleft, PyObject *right)
+
+   Concat two strings and put the result in *pleft. Sets *pleft to
+   NULL on error.
+
+.. c:function:: void PyUnicode_AppendAndDel(PyObject **pleft, PyObject *right)
+
+   Concat two strings and put the result in *pleft and drop the right
+   object. Sets *pleft to NULL on error.
+
+

Please don't document these two obscure APIs. Instead we should
make them private functions by prepending them with an underscore.
If you look at the implementations of those two APIs, they
are little more than a macros around PyUnicode_Concat().

3rd party extensions should use PyUnicode_Concat() to achieve
the same effect.
"""

While it is OK for Python library to use private APIs, please consider if PyUnicode_Concat() may be more appropriate.  If not, please make a case at issue 10435 for keeping it public.
History
Date User Action Args
2010-11-19 15:23:09belopolskysetrecipients: + belopolsky, lemburg, georg.brandl, rhettinger, terry.reedy, thomaslee, eric.araujo, stribb, daniel.urban
2010-11-19 15:23:09belopolskysetmessageid: <1290180189.3.0.982102818074.issue4113@psf.upfronthosting.co.za>
2010-11-19 15:23:08belopolskylinkissue4113 messages
2010-11-19 15:23:08belopolskycreate