You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PEP-703 explains the risky situation of borrowed reference API.
For working on #111926, I think that we should introduce a new API with strong reference that was named PyWeakref_FetchObject from the PEP.
But to follow the recent convention, the API name will be PyWeakref_GetObjectRef.
Since SC approved the PEP, there would be no issue with adding this API.
However I want to listen to opinions from a few core devs before working on the task.
PEP-703 explains the risky situation of borrowed reference API.
For working on #111926, I think that we should introduce a new API with strong reference that was named
PyWeakref_FetchObject
from the PEP.But to follow the recent convention, the API name will be
PyWeakref_GetObjectRef
.Since SC approved the PEP, there would be no issue with adding this API.
However I want to listen to opinions from a few core devs before working on the task.
@encukou @colesbury @vstinner
The text was updated successfully, but these errors were encountered: