Fix the inconsistent usage of #if [!]defined XXX compared to defined(XXX)Thanks-to: Pierre JolivetAn LLM Claude detected the incosnsitency it was not used to remove the inconsistency
Add automatic generated fortran support for setting and returning contextsMajor cleanup of the code for setting and returning application (previously called user) contexts - PetscCtx ctx is now t
Add automatic generated fortran support for setting and returning contextsMajor cleanup of the code for setting and returning application (previously called user) contexts - PetscCtx ctx is now the standard for passing in contexts - PetscCtxRt ctx is the standard for passing out contexts, including context destroy routines based on PetscCtxDestroyFnBoth of these are typedef to void*Also removed most use of user and userctx for context arguments now consistently named ctxImproved documentation on PetscCtx and PetscCtxRt and on how to use contexts (including getting them) from Fortran
show more ...
Run fprettify
Fixes suggested by Fortitude to Fortran code (minor)
Merge remote-tracking branch 'origin/release'
Remove use of preconditioning or preconditioner matrix when it should be phrased as matrix used to construct preconditioner
Add support for --download-dolphinx and its needed packagesAlso add saving of pythonpath and PYTHONPATH in pkgconfig and petscvariables for users to access
Fortran 90: fully embrace After 34 years!- deprecate use of 'F90' in Fortran function names- use Fortran pointers when appropriate- the new Fortran API is not backward compatible with previous ve
Fortran 90: fully embrace After 34 years!- deprecate use of 'F90' in Fortran function names- use Fortran pointers when appropriate- the new Fortran API is not backward compatible with previous versions!- also clean up inconsistent PETSc code detected by new Fortran generation tools- drop use of bfort- automatically generate all the Fortran PETSc objects, enums etc from the include files- generate most of the Fortran interface definitions and functions from the source code- simplify the number and organization of Fortran modulesCo-authored-by: Jose E. Roman <jroman@dsic.upv.es>
petsc4py: modernize legacy ode demos
Add python APIs
Add an error check for DMSetFromOptions() being called after DMSetUp().Reported-by: Jack Smith
petsc4py: finalize docstring and lintingdefault options values should have the correct typefix testsconform oarray to PETSc conventionwrap Py_InitializeEx and PyImport_ImportModule with stack ca
petsc4py: finalize docstring and lintingdefault options values should have the correct typefix testsconform oarray to PETSc conventionwrap Py_InitializeEx and PyImport_ImportModule with stack callsupdate makefile for docs and linting rulesadd petsc4py tests to linux-pkgs-dbgmodify documentation
Minor changes in petsc4py manual
checkbadSource: rules for PetscFunctionBegin and derivatives
Remove duplicates and switch to python3
petsc4py documentation sprint (Faversham, England, 2023)Co-authored-by: Jack Betteridge <j.betteridge@imperial.ac.uk>Co-authored-by: Nathan Collier <nathaniel.collier@gmail.com>Co-authored-by: Li
petsc4py documentation sprint (Faversham, England, 2023)Co-authored-by: Jack Betteridge <j.betteridge@imperial.ac.uk>Co-authored-by: Nathan Collier <nathaniel.collier@gmail.com>Co-authored-by: Lisandro Dalcin <dalcinl@gmail.com>Co-authored-by: Iglesia Dolci <daia.dolci@gmail.com>Co-authored-by: David Ham <david.ham@imperial.ac.uk>Co-authored-by: Marcin Rogowski <marcin.rogowski@gmail.com>Co-authored-by: Koki Sagiyama <k.sagiyama@imperial.ac.uk>Co-authored-by: Connor Ward <c.ward20@imperial.ac.uk>Co-authored-by: Stefano Zampini <stefano.zampini@gmail.com>