> I'm sceptical that these would find use in practice.<br>> [..]<br>> Also, I question the utility of maintaining a weakref to a method or<br>> attribute instead of holding one for the object or class. As long as
<br>> the enclosing object or class lives, so too will their methods and<br>> attributes. So what is the point of a tighter weakref granualarity?<br><br>i didn't just came up with them "out of boredom", i have had specific
<br>use cases for these, mainly in rpyc3000... but since the rpyc300 <br>code base is still far from completion, i don't want to give examples <br>at this early stage.<br><br>however, these two are theoretically useful, so i refactored them out
<br>of my code into recipes.<br><br><br>-tomer<br><br><div><span class="gmail_quote">On 9/28/06, <b class="gmail_sendername">Raymond Hettinger</b> <<a href="mailto:python@rcn.com">python@rcn.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Also, I question the utility of maintaining a weakref to a method or<br>> attribute instead of holding one for the object or class.<br><br>Strike that paragraph -- the proposed weakattrs have references away from the
<br>object, not to the object.<br><br><br>Raymond<br></blockquote></div><br>