Searched refs:trash (Results 1 – 3 of 3) sorted by relevance
41 trash (CT) exists, then any call to any Python code whatsoever can end up59 Clearing cyclic trash can call Python code. If there are weakrefs to60 any of the cyclic trash, then those weakrefs can be used to resurrect61 the objects. Therefore, *before* clearing cyclic trash, we need to83 is that the weakly referenced object is unreachable trash at the time the87 becomes part of a clump of cyclic trash. When enough cycles are broken by102 Note that if it's possible for the callback to get at objects in the trash104 trash cycles. Else the callback would have acted as an external root to106 trash either.111 More, if the callback itself is in cyclic trash, then the weakref to which[all …]
31 …- ".trash" contains sections taht GCC simply feel like it MUST produce (link error otherwise) but …45 trash : ORIGIN = 0xF0000000, LENGTH = 256K /* we throw this away soon after linking */136 } > trash139 } > trash142 } > trash
3855 class trash(object): class3861 o = trash(o)