aspectlib.debug.log doesn't play nice with weak references about python-aspectlib HOT 4 CLOSED

The __logged__ is missing the __weakref__ slot. I can humour your request and add it but it doesn't look very useful overall. Methods are most always new objects - if you don't hold other references to them they are going to be garbage collected immediately. Eg, in your example your set is always going to be empty on py2.7. Py3 seems to have some sort of caching for methods accessed via the class. Why do you need weakrefs for methods anyway?

from python-aspectlib.

I have no use for it, but apparently the original author of the code I'm
trying to debug likes to keep weakrefs to callables for reasons I don't
understand.

On 25 November 2014 at 10:34, Ionel Cristian Mărieș <
[email protected]> wrote:

Closed #1 #1 via
5a32568
5a32568
.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from python-aspectlib.

Alright. I've made a 1.2.2 release. Let me know if you have further issues.

from python-aspectlib.

Fantastic, thanks for that.

On 25 Nov 2014, at 13:44, Ionel Cristian Mărieș [email protected] wrote:

Alright. I've make a 1.2.2 release. Let me know if you have further issues.

—
Reply to this email directly or view it on GitHub.

from python-aspectlib.