Re: [Pyunit-interest] Traceback objects stored in PyUnit error lists
Brought to you by:
purcell
|
From: Fred L. D. Jr. <fd...@ac...> - 2001-08-28 16:27:58
|
Steve Purcell writes: > 1. Have you ever been bitten by the unexpected lack of garbage collection? Not directly, but I think this will bite Windows users more than Unix users. The problem is that open files have more consequences on Windows than on Unix (you can't rename or unlink it), so there are more ways for open file objects to cause failures there. > 2. Do you have custom TestRunner code that would be affected by such a > change? I don't think so, but if so, they can be fixed easily enough. For people that want to use the exception for debugging support, it probably makes more sense to debug immediately rather than storage a bunch of tracebacks to the end. For just about any package, it is very easy to have side effects (intentional or otherwise) that affect the objects referenced by stored tracebacks, so debugging using the stored traceback is less effective than debugging immediately. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation |