-
Notifications
You must be signed in to change notification settings - Fork 177
Firedrake meeting 2022 11 09
JDBetteridge edited this page Nov 9, 2022
·
6 revisions
Date and time 2022-11-09 16:00UTC
- Pick Chair and Minuter (CW to pick minuter)
- ALL: (ongoing) triage the open issues and confirm if they are indeed still open (and perhaps provide labels)
- DH: Organise Firedrake 2022 (Abstracts open)
- ALL: Rename split (
.split->.subfunctions) (ongoing) - JB: A Firedrake manual (ongoing)
- JB: Python 3.11 (ongoing)
Present:
Apologies:
(Low priority) We have had the conversation before in the past: Should we use black to autoformat code?
Some formatting is inconsistent/bad. I have used black in a recent PR to cleanup utility_meshes.py.
(Low priority) This PR changes testing from Python 3.6 to Python 3.7-3.11, is the matrix worth it? Should PyOP2 use our Firedrake runners? Should we move PyOP2 to Firedrake organisation?
JB: Versioneer finally removed distutils dependency, so these are ready to go:
JB: We can ignore this failing test (I think) https://github.com/firedrakeproject/firedrake/pull/2613
1600 UTC 2022-11-16