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/2009-June/090097.html below:

[Python-Dev] Functions that steal references (Re: [pygame] [patch] minor memory leaks...)

[Python-Dev] Functions that steal references (Re: [pygame] [patch] minor memory leaks...)Benjamin Peterson benjamin at python.org
Wed Jun 17 01:05:08 CEST 2009
2009/6/16 Greg Ewing <greg.ewing at canterbury.ac.nz>:
> Lenard Lindstrom wrote:
>
>> I assumed that since PyModule_AddObject is documented as stealing a
>> reference, it always stole a reference. But in reality it only does so
>> conditionally, when it succeeds.
>
> As an aside, is this a general feature of functions
> that steal references, or is PyModule_AddObject an
> oddity?

IIRC, It's an oddity.
>
> I ask because I've been thinking about adding features
> to Pyrex for dealing with stolen references, and it
> could be important to know things like this.
>
> Also, if it's an oddity, it would be a good idea
> to mention this behaviour in the docs.

Yes, indeed.



-- 
Regards,
Benjamin
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