Warn if PETSc is already initialised inside petsctools.init.#38
Conversation
This functionality was rejected from petsc4py and so should live here. It is unfortunately complicated due to the petsc4py init process. Also tidies up some docstrings and moves some exceptions to exceptions.py which is now the established convention.
|
I'm sure I've seen this warning pop up when running the Firedrake test suite recently. Was I accidentally on this petsctools branch or a PETSc branch with the warning without realising or have I been hallucinating?? |
See https://gitlab.com/petsc/petsc/-/merge_requests/9353. It was in petsc4py but I then got asked to take it out. |
Gotcha. This looks fine then. |
2 participants
This functionality was rejected from petsc4py and so should live here. It is unfortunately complicated due to the petsc4py init process.
Also tidies up some docstrings and moves some exceptions to exceptions.py which is now the established convention.