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 eltoder
Recipients asvetlov, christian.heimes, daniel.urban, eltoder, jcea, pitrou, python-dev
Date 2012-12-08.20:42:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thank you, Antoine.
This change has one effect that's worth highlighting in NEWS at least -- the PyWeakref_GET_OBJECT() macro now evaluates its argument twice. This can break existing code where the argument has side-effects, e.g. o = PyWeakref_GET_OBJECT(p++). I found one such case in our code base, but I don't know how common this is. So this is something to watch out for when upgrading.
I don't think there's a way to write PyWeakref_GET_OBJECT() in standard C90 without double evaluation.
Date User Action Args
2012-12-08 20:42:00eltodersetrecipients: + eltoder, jcea, pitrou, christian.heimes, asvetlov, daniel.urban, python-dev
2012-12-08 20:42:00eltodersetmessageid: <>
2012-12-08 20:42:00eltoderlinkissue16602 messages
2012-12-08 20:42:00eltodercreate