➜

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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, asvetlov, christian.heimes, daniel.urban, eltoder, jcea, pitrou, python-dev
Date 2012-12-10.10:13:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355134393.26.0.0609033862182.issue16602@psf.upfronthosting.co.za>
In-reply-to
Content 
PyWeakref_GET_OBJECT is also potentially dangerous: since the refcount is not incremented, it's very possible that the GC collects it.

The only safe operation after PyWeakref_GET_OBJECT is to Py_XINCREF the result. Should we provide a PyWeakRef_LockObject()?
History
Date User Action Args
2012-12-10 10:13:13amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, jcea, pitrou, christian.heimes, asvetlov, daniel.urban, python-dev, eltoder
2012-12-10 10:13:13amaury.forgeotdarcsetmessageid: <1355134393.26.0.0609033862182.issue16602@psf.upfronthosting.co.za>
2012-12-10 10:13:13amaury.forgeotdarclinkissue16602 messages
2012-12-10 10:13:13amaury.forgeotdarccreate