A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-April/134094.html below:

[Python-Dev] is the concept of 'reference ownership' no long applicable in Python 3.4?

[Python-Dev] is the concept of 'reference ownership' no long applicable in Python 3.4? [Python-Dev] is the concept of 'reference ownership' no long applicable in Python 3.4?Mark Dickinson dickinsm at gmail.com
Thu Apr 17 18:33:38 CEST 2014
On Thu, Apr 17, 2014 at 4:34 PM, Jianfeng Mao <jmao at rocketsoftware.com>wrote:

>  I noticed the following changes in the C API manuals from 3.3.5 (and
> earlier versions) to 3.4. I don’t know if these changes are deliberate and
> imply that we C extension developers no longer need to care about
> ‘reference ownership’ because of some improvements in 3.4. Could anyone
> clarify it?
>

AFAIK there's been no deliberate change to the notion of reference
ownership.  Moreover, any such change would break existing C extensions, so
it's highly unlikely that anything's changed here, behaviour-wise.

This looks like a doc build issue: when I build the documentation locally
for the default branch, I still see the expected "Return value: New
reference." lines.  Maybe something went wrong with refcounts.dat or the
Sphinx refcounting extension when building the 3.4 documentation?  Larry:
any ideas?

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140417/0165bd5a/attachment.html>
More information about the Python-Dev mailing list

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