Skip to content

Introduce separate requirements-build.txt#242

Merged
stephankramer merged 1 commit into
releasefrom
skramer/add-requirements-build.txt
Jun 12, 2026
Merged

Introduce separate requirements-build.txt#242
stephankramer merged 1 commit into
releasefrom
skramer/add-requirements-build.txt

Conversation

@stephankramer

Copy link
Copy Markdown
Member

Same as #241, see description there

Doing this before merging main into release (see #239) because I first want to fix the building of the firedrake-parmmg:release container which needs the additional requirements-build.txt step. After adding the step in "docs", it should then build again, but the animate tests will fail, which I will then address in #239.

Note that this merge has cherry-picked the commit from #241, which is not normally what we want to do as we end up with the same commit twice after merging main into release but I will deal with that in #239.

This is needed because we are instructing our users to build
with `pip install --no-build-isolation` which tells pip to build in the
current python env and ignores the build dependencies specified in
pyproject.toml. Following the installation instructions for Firedrake
release however, this environment may not have these build requirements
installed already (notably Cython and a sufficiently new setuptools).
Therefore we need to instruct users to run `pip install -r
animate/requirements-build.txt` beforehand.

TODO (after merge):
* update wiki installation instructions
* use the additional step in the CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants