petsc4py: Silence Cython warnings
performance hint: petsc4py/PETSc/PETSc.pyx:67:5: Exception check on 'SETERR' will always require the GIL to be acquired. Possible solutions:
1. Declare the functio
petsc4py: Silence Cython warnings
performance hint: petsc4py/PETSc/PETSc.pyx:67:5: Exception check on 'SETERR' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/petscdmda.pxi:116:5: Exception check on 'DMDAGetDim' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:36:5: Exception check on 'FunctionBegin' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:45:5: Exception check on 'FunctionEnd' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:54:5: Exception check on 'PetscSETERR' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:61:5: Exception check on 'UNSUPPORTED' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:72:5: Exception check on 'addRef' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:76:5: Exception check on 'delRef' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/PETSc.pyx:272:5: Exception check on 'traceback' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/PETSc.pyx:312:5: Exception check on 'PetscPythonErrorHandler' will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/PETSc.pyx:79:16: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:495:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:509:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1335:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1344:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1396:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1398:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1641:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1650:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1692:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1696:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:1992:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2001:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2045:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2047:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2343:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2352:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2407:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2411:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2759:17: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
performance hint: petsc4py/PETSc/libpetsc4py.pyx:2768:22: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: petsc4py/PETSc/PETSc.pyx:324:24: Exception check will always require the GIL to be acquired. Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
show more ...
|