On Wed, Aug 05, 2009 at 09:51:00AM -0700, Christopher Lee wrote: -> Hmm. Maybe deleting the object isn't triggering garbage collection?
No, but I am doing so manually. So there are internal references that gc.collect() cannot get rid of... which, since it uses mark-and-sweep, means that somewhere there is a reference to them, either in module globals OR the sequence database. It's not a Pyrex problem, at least not by my understanding of how garbage collection works in Python. -> I'll try to enumerate the various places a reference to the sequence -> object might be held, in another email. That would be helpful, yes! I will also try some forensic code analysis (i.e. lots of print statements) to figure out where references are getting created and then dig into that code. thanks, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
