Fix version numbers for dune package requirements
At the moment we (mostly) don't fix specific versions for the PythonRequirements
in dune.module
- except for pip>=21
and setuptools>=41
. I just now ran into the problem that the binding code didn't work correctly with a newer numpy
version due to a change in the dtype.format
value (changed from Q
to <Q
).
Should we fix versions (or at least ranges if possible) for those packages?
Advantage: code will be more stable and less issues report by users
Disadvantage: more difficult to mix code, i.e., we now have some projects with students mixing fenics
and dune
or using petsc4py
if those package were to set other version requirements (which would actually be fine for dune) then that becomes impossible.
A possible compromise would be to add specific version of the required packages into the internal venv but not into an active external venv and making it clear that we support stability with respect to package version only when using the internal venv. But that might look inconsistent.