[issue34830] functools.partial is weak referncable

2018-09-28 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Instances of many builtin types are not weak referencable. >>> weakref.ref(0) Traceback (most recent call last): File "", line 1, in TypeError: cannot create weak reference to 'int' object >>> weakref.ref([]) Traceback (most recent call last): File "",

[issue34830] functools.partial is weak referncable

2018-09-28 Thread Julien Palard
Change by Julien Palard : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-

[issue34830] functools.partial is weak referncable

2018-09-28 Thread Julien Palard
Julien Palard added the comment: TIL. So it really make sense in this context to tell a functools.partial is weak referencable? -- ___ Python tracker ___ ___

[issue34830] functools.partial is weak referncable

2018-09-28 Thread Andrew Svetlov
Andrew Svetlov added the comment: I think yes. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue34830] functools.partial is weak referncable

2018-09-28 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue34830] functools.partial is weak referncable

2018-09-28 Thread Andrew Svetlov
Andrew Svetlov added the comment: ``` In [1]: import weakref In [2]: class A: ...: __slots__ = ()

[issue34830] functools.partial is weak referncable

2018-09-28 Thread Julien Palard
New submission from Julien Palard : According to the doc: :class:`partial` objects are like :class:`function` objects in that they are callable, weak referencable, and can have attributes. I don't understand why "weak" here, and it's the only occurence of "weak referencable" in the docum