[Python-Dev] Debugging opportunity :-) (original) (raw)
Tim Peters tim.peters at gmail.com
Sat Apr 15 05:02:37 CEST 2006
- Previous message: [Python-Dev] Debugging opportunity :-)
- Next message: [Python-Dev] valgrind reports
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Phillip J. Eby]
Even with the close() gimmicks still in place? If so, it sounds like the safest thing for a2 might be to claim that generators always need finalizing. :(
LOL! Been there many times before: Python's gc really does work, but it's as unforgivingly delicate as any dance you're likely to learn while still mortal :-) This one was actually typical, ending with an unlikely comedy of errors involving microscopic details of how multiple objects' cleanup routines could barely manage to fool each other into tearing down an object more than once. Until you get to that point of clarity, it's also typical to fear that it can never be fixed ;-)
You and Thomas did a wonderful of job of tracking this one down quickly. Good show! Take Easter off -- but only if you have to :-)
- Previous message: [Python-Dev] Debugging opportunity :-)
- Next message: [Python-Dev] valgrind reports
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]