[petsc-dev] Remove calls to XXXReset() in XXXDestroy()

[Jed Brown]

On Fri, May 13, 2011 at 15:25, Lisandro Dalcin <dalcinl at gmail.com> wrote:

> Python could be even harder than
> C++, because of the GC that can start running at any time.
>

Is it _ever_ acceptable to let the garbage collector manage destruction of
PETSc objects? It seems to me that you can't ever take this chance with
objects that may be parallel. This includes objects that may be destroyed
explicitly when a 'with' block exits or a 'finally' block is reached due to
an exception that is not collective. Under what circumstances does the GC
running affect PETSc objects in any way?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110513/3ff32f41/attachment.html>