[issue43252] deepcopy of weakref proxies

2021-04-15 Thread Konrad Schwarz
Konrad Schwarz added the comment: Well, in the example code, the memo dictionary contains the (hard) reference to newly created objects but ultimately, at the close of the deepcopy, the objects are (hard) referenced using the normal "child" attributes. I don't however know how

[issue43383] imprecise handling of weakref callbacks

2021-03-04 Thread Konrad Schwarz
Change by Konrad Schwarz : -- resolution: -> postponed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue43383] imprecise handling of weakref callbacks

2021-03-04 Thread Konrad Schwarz
Konrad Schwarz added the comment: Unfortunately, my management has impressed other priorities upon me; I can't delve deeper into this subject at the moment. My takeaway is that the error very likely lies on my side; maybe I need to re-check local variables and del them explicitly. In any

[issue43383] imprecise handling of weakref callbacks

2021-03-03 Thread Konrad Schwarz
Konrad Schwarz added the comment: > If I understand correctly, the reported bug is that you're seeing a weakref > callback being executed > after the weakref.ref instance it's attached to is deleted. Is that correct? Exactly. I del what should be the only reference to the weakref.

[issue43383] imprecise handling of weakref callbacks

2021-03-02 Thread Konrad Schwarz
New submission from Konrad Schwarz : I am seeing the following non-deterministic behavior: My code processes DeviceTree, a tree-based specification format for hardware descriptions, that includes cross-references ("phandles"). For all intents and purposes, this format is simi

[issue43252] deepcopy of weakref proxies

2021-02-18 Thread Konrad Schwarz
New submission from Konrad Schwarz : copy.deepcopy()-ing a tree structure that has internal parent and cross-reference links implemented as weakref.proxy() objects causes the weak reference proxies themselves to be copied (still refering to their original referents) rather than weak

[issue42324] Doctest: directives

2020-11-11 Thread Konrad Schwarz
Konrad Schwarz added the comment: Yes it is. On Wed, Nov 11, 2020 at 1:06 PM Karthikeyan Singaravelan < rep...@bugs.python.org> wrote: > > Karthikeyan Singaravelan added the comment: > > Is this similar to https://bugs.python.org/issue36675 ? > > --

[issue42324] Doctest: directives

2020-11-11 Thread Konrad Schwarz
New submission from Konrad Schwarz : In both PDF and HTML, the examples for Doctest directives don't actually show the directives themselves, perhaps because they syntactically start with a #. -- assignee: docs@python components: Documentation messages: 380752 nosy: docs@python