
doesn't seem to work for me... --- Don't be humble ... you're not that great. -- Golda Meir

My stupid mistake. I forgot to add a filter rule to my mail client to put the lxml mail into it's own folder. The last filter I have puts all email from myself into a special folder - so I never saw my emails. Anyway- my stupid mistake. It's fixed now. I'll take a look at your memory management ideas - at first glance, I think you're making the problem a lot harder than it needs to be. vic --- Don't be humble ... you're not that great. -- Golda Meir On 29-Sep-04, at 12:37 PM, Martijn Faassen wrote:

vng1@mac.com wrote:
That would be good. The problem is a lot easier when the tree is read-only in Python, but as soon as you're able to detach parts of the tree, it gets pretty hairy. My goal in that this is to rely on Python's refcounting to do the main job. For a read-only tree that's simple enough; each node proxy in Python has a reference to the document proxy. When the document proxy is not referenced anymore, the whole tree is freed. That strategy doesn't hold up in the face of nodes created that are not (immediately or ever) attached to the main tree. Regards, Martijn

My stupid mistake. I forgot to add a filter rule to my mail client to put the lxml mail into it's own folder. The last filter I have puts all email from myself into a special folder - so I never saw my emails. Anyway- my stupid mistake. It's fixed now. I'll take a look at your memory management ideas - at first glance, I think you're making the problem a lot harder than it needs to be. vic --- Don't be humble ... you're not that great. -- Golda Meir On 29-Sep-04, at 12:37 PM, Martijn Faassen wrote:

vng1@mac.com wrote:
That would be good. The problem is a lot easier when the tree is read-only in Python, but as soon as you're able to detach parts of the tree, it gets pretty hairy. My goal in that this is to rely on Python's refcounting to do the main job. For a read-only tree that's simple enough; each node proxy in Python has a reference to the document proxy. When the document proxy is not referenced anymore, the whole tree is freed. That strategy doesn't hold up in the face of nodes created that are not (immediately or ever) attached to the main tree. Regards, Martijn
participants (2)
-
Martijn Faassen
-
vng1@mac.com