Showing content from http://mail.python.org/pipermail/python-dev/attachments/20161010/f96b2ce1/attachment.html below:
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
The documentation for PyWeakref_GetObject() states:<br>
<blockquote>Return value: Borrowed reference.<br>
<br>
Return the referenced object from a weak reference, ref. If the
referent is no longer live, returns Py_None.<br>
</blockquote>
Given that the weakref doesn't have a reference to the
object--merely a weak reference, different thing--whose reference is
it borrowing?<br>
<br>
FWIW, yes, this is playing merry hell with the Gilectomy. If there
are two threads, and one calls PyWeakref_GetObject(obj), and there's
only one reference to obj, and the other thread blows it away... now
what? It's my contention that this API is simply untenable under
the Gilectomy, and that it needs to change to returning a new
(strong) reference.<br>
<br>
<br>
<i>/arry</i><br>
</body>
</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