{tools}[foss/2023b] petsc4py v3.20.3#20569
{tools}[foss/2023b] petsc4py v3.20.3#20569tanmoy1989 wants to merge 6 commits intoeasybuilders:developfrom
Conversation
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
Updated software
|
|
Can you update the PR title and link to the dependency PR (22084) |
|
Test report by @Flamefire |
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
|
Test report by @Flamefire |
|
Test report by @Flamefire |
Co-authored-by: Lara Ramona Peeters <49882639+laraPPr@users.noreply.github.com>
|
Can you update the PR title and filename please @laraPPr 3.22.5 isn't available via PyPI, 3.22.4 is the latest there A download is available from https://gitlab.com/petsc/petsc/-/archive/v3.22.5/petsc-v3.22.5.tar.gz (https://gitlab.com/petsc/petsc) after they incorporated petsc4py:
The petsc4py GitLab repo is archived too:
|
|
As @Flamefire mentioned, the source code for petsc4py is now distributed with PETSc. There has been no release of petsc4py version 3.22.5 in PyPI. This is a problem because petsc4py and PETSc versions must agree and PETSc v3.22.5 has been added in the foss/2023b toolchain. The PR #23581 resolves the issue by building petsc4py v3.22.5 from source code of the bindings of PETSc v3.22.5. @tanmoy1989 @laraPPr @moravveji Maybe we can close this PR and update PRs that depend on it? |
|
@Flamefire : I am bit confused. What do you suggest as the new title for this PR and the new filename? |
@tanmoy1989 changed the version to 3.22.5 int the file after suggestion from @laraPPr but the filename didn't change and the PR title also refers to the old version making this hard to find. That new PR looks good, so we could use that instead of fixing this. |
|
Do we still need that as we got |
|
I think we don't need this as the same version 3.22.5 was merged with #23581 |
(created using
eb --new-pr)