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 josh.r
Recipients BreamoreBoy, baruch.sterin, docs@python, josh.r, meador.inge
Date 2014-07-04.00:39:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1404434371.56.0.586553012778.issue14189@psf.upfronthosting.co.za>
In-reply-to
Content
If any of these actually return borrowed references, I'd consider it a serious documentation bug to not mention it. New reference semantics are the default, and while it's best to call them out, it can be assumed in most cases. Returning borrowed references without a big honking "not a normal function" flag in the docs causes a big problem.

Heck, the lack of such a big warning flag on PyDict_Next (which doesn't return a PyObject, but populates via a double pointer) caused me a major headache recently when I DECREF-ed the resulting objects. Totally my fault (the description says they're borrowed), but I rely on that "Returns: Borrowed Reference" header so much that I made a dumb mistake.
History
Date User Action Args
2014-07-04 00:39:31josh.rsetrecipients: + josh.r, meador.inge, docs@python, BreamoreBoy, baruch.sterin
2014-07-04 00:39:31josh.rsetmessageid: <1404434371.56.0.586553012778.issue14189@psf.upfronthosting.co.za>
2014-07-04 00:39:31josh.rlinkissue14189 messages
2014-07-04 00:39:30josh.rcreate