Restoring authorship annotation for <[email protected]>. Commit 1 of 2.

1 files changed, 11 insertions, 11 deletions

diff --git a/contrib/tools/python/src/Include/weakrefobject.h b/contrib/tools/python/src/Include/weakrefobject.h
index e7c0eae5398..eab56ffb1a4 100644
--- a/contrib/tools/python/src/Include/weakrefobject.h
+++ b/contrib/tools/python/src/Include/weakrefobject.h
@@ -63,19 +63,19 @@ PyAPI_FUNC(Py_ssize_t) _PyWeakref_GetWeakrefCount(PyWeakReference *head);
 
 PyAPI_FUNC(void) _PyWeakref_ClearRef(PyWeakReference *self);
 
-/* Explanation for the Py_REFCNT() check: when a weakref's target is part
-   of a long chain of deallocations which triggers the trashcan mechanism,
-   clearing the weakrefs can be delayed long after the target's refcount
-   has dropped to zero.  In the meantime, code accessing the weakref will
-   be able to "see" the target object even though it is supposed to be
-   unreachable.  See issue #16602. */
-
-#define PyWeakref_GET_OBJECT(ref)                           \
-    (Py_REFCNT(((PyWeakReference *)(ref))->wr_object) > 0   \
-     ? ((PyWeakReference *)(ref))->wr_object                \
-     : Py_None)
+/* Explanation for the Py_REFCNT() check: when a weakref's target is part 
+   of a long chain of deallocations which triggers the trashcan mechanism, 
+   clearing the weakrefs can be delayed long after the target's refcount 
+   has dropped to zero.  In the meantime, code accessing the weakref will 
+   be able to "see" the target object even though it is supposed to be 
+   unreachable.  See issue #16602. */ 
 
+#define PyWeakref_GET_OBJECT(ref)                           \ 
+    (Py_REFCNT(((PyWeakReference *)(ref))->wr_object) > 0   \ 
+     ? ((PyWeakReference *)(ref))->wr_object                \ 
+     : Py_None) 
 
+ 
 #ifdef __cplusplus
 }
 #endif