History log of /petsc/src/binding/petsc4py/docs/source/install.rst (Results 1 – 25 of 35)
Revision Date Author Comments
# 8aa39e1b 30-Jun-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'release'


# 7cbcdb4f 27-Jun-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini/petsc4py-snes' into 'release'

petsc4py: add bindings for SNESLineSearch and SNESNEWTONAL

See merge request petsc/petsc!8467


# 88386097 09-Jun-2025 Stefano Zampini <stefano.zampini@gmail.com>

petsc4py: reinstate instructions for building docs

amend changes from 34c645fd3b0199e05bec2fcc32d3597bfeb7f4f2


# 0d821f60 30-Apr-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'release'


# c24104ab 30-Apr-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini/relocatable-wheels' into 'release'

support relocatable wheel file

See merge request petsc/petsc!8354


# 6e8294f6 28-Apr-2025 Stefano Zampini <stefano.zampini@gmail.com>

setup.py: support python env relocation when building wheel

remove mpi4py dependency on the setup process
replace symlinked .so library with INPUT text file


# 174dc0c8 28-Apr-2025 Satish Balay <balay@mcs.anl.gov>

Merge remote-tracking branch 'origin/release'


# dfa41899 25-Apr-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini-release-patch-26701' into 'release'

Edit install.rst

See merge request petsc/petsc!8344


# 8348cc77 24-Apr-2025 Stefano Zampini <stefano.zampini@gmail.com>

Edit install.rst


# 7c485f38 09-Jul-2024 Satish Balay <balay@mcs.anl.gov>

Merge remote-tracking branch 'origin/release'


# 91fd0dc0 09-Jul-2024 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2024-07-08/minor-plex-docs/release' into 'release'

Build PETSc and petsc4py docs with the same requirements file

See merge request petsc/petsc!7678


# 34c645fd 08-Jul-2024 Barry Smith <bsmith@mcs.anl.gov>

Update sphinx packages used to build docs make petsc4py docs shared common requirements.txt

This prevents errors such as below when building docs

Running Sphinx v7.3.7
Using PETSC inventory from fi

Update sphinx packages used to build docs make petsc4py docs shared common requirements.txt

This prevents errors such as below when building docs

Running Sphinx v7.3.7
Using PETSC inventory from file:///Users/barrysmith/Src/petsc/doc/_build/html/objects.inv
<Inventory (url): PETSc v3.21, 7842 objects>

Exception occurred:
File "petsc4py/PETSc.pyx", line 1, in init petsc4py.PETSc
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

show more ...


# 552edb63 18-Apr-2024 Satish Balay <balay@mcs.anl.gov>

Merge remote-tracking branch 'origin/release'


# 10fdf553 18-Apr-2024 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini/fix-petsc4py' into 'release'

petsc4py: finalize docstrings and linting

See merge request petsc/petsc!7467


# 6f336411 09-Apr-2024 Stefano Zampini <stefano.zampini@gmail.com>

petsc4py: finalize docstring and linting

default options values should have the correct type
fix tests
conform oarray to PETSc convention
wrap Py_InitializeEx and PyImport_ImportModule with stack ca

petsc4py: finalize docstring and linting

default options values should have the correct type
fix tests
conform oarray to PETSc convention
wrap Py_InitializeEx and PyImport_ImportModule with stack calls
update makefile for docs and linting rules
add petsc4py tests to linux-pkgs-dbg
modify documentation

show more ...


# 6996bd1a 21-Feb-2024 Satish Balay <balay@mcs.anl.gov>

Merge branch 'jolivet/fix-double' into 'main'

Fix words appearing twice in a row for no good reason

See merge request petsc/petsc!7307


# 15229ffc 21-Feb-2024 Pierre Jolivet <pierre@joliv.et>

Fix words appearing twice in a row for no good reason


# 98340805 21-Jun-2023 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini/petsc4pydocs-usermeeting' into 'main'

petsc4py docstrings: add links to the source code and activate some standards checking

See merge request petsc/petsc!6578


# cabd1581 05-Jun-2023 Stefano Zampini <stefano.zampini@gmail.com>

petsc4py docs: minor fixes


# 5a48edb9 16-Apr-2023 Satish Balay <balay@mcs.anl.gov>

Merge branch 'dalcinl/petsc4py-docs' into 'main'

petsc4py documentation sprint (Faversham, England, 2023)

See merge request petsc/petsc!6313


# 55a74a43 12-Apr-2023 Lisandro Dalcin <dalcinl@gmail.com>

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>

show more ...


# 02d2f6e8 04-May-2021 Satish Balay <balay@mcs.anl.gov>

Merge branch 'PR--config-cross-compilation' into 'main'

config,petsc4py: support cross-compilation

See merge request petsc/petsc!3859


# 0f51ee0f 12-Apr-2021 Alexei Colin <acolin@isi.edu>

config,petsc4py: support cross-compilation

On some HPC clusters it is necessary to cross-compile because the build hosts
(login nodes) have a different architecture (or CPU family) from worker ndoes

config,petsc4py: support cross-compilation

On some HPC clusters it is necessary to cross-compile because the build hosts
(login nodes) have a different architecture (or CPU family) from worker ndoes,
for example on ALCF Theta HPC cluster workers are Xeon Phi, so turning on
cpu-family optimizations turns the build into a cross-compilation. The current
./configure fails with SIGILL (Illegal instruction) when it tries to import
`numpy`, which had been cross-compiled and cannot run on the build host.

This patch simply adds (to `./configure` and to `petsc4py`'s `setup.py`) a
means to suppress autodetection operations that involve loading dependencies
for checks and to get meta info like include. Users who cross-compile can use
these arguments to pass the meta info explicitly so that it doesn't need to
be autodetected on the build host.

To interface into `setup.py` an env var is used, because there doesn't seem
to be any better alternative. We don't want to mess with setuptools's
built-in processing of command-line arguments; and extending that seems to
be possible only per command, which is not useful for getting the information
we need at the top-level scope and is also needlessly complicated.

Signed-off-by: Alexei Colin <acolin@isi.edu>

show more ...


# d7bfff7c 03-May-2021 Satish Balay <balay@mcs.anl.gov>

Merge remote-tracking branch 'origin/release'


# c2d36b98 03-May-2021 Satish Balay <balay@mcs.anl.gov>

Merge branch 'PR--petsc4py-doc-install' into 'release'

petsc4py: docs: detailed instructions for building from source

See merge request petsc/petsc!3939


12