-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing fenics adapter may break FEniCS installation #103
Comments
This is a sporadic issue. We will keep it open as an information for users, but won't fix it until we can reproduce it. |
I guess we can reproduce the problem with this docker file: https://github.com/uekerman/Coupled-Brittle-Fracture/blob/master/brittle-fracture.dockerfile |
The Dockerfile from https://fenicsproject.discourse.group/t/installing-python-package-with-fenics-dependency-breaks-fenics-installation/4476 allows us to reproduce the error. I think this is a upstream issue, where we currently cannot do anything. |
From my understanding, Hence, My best guess is that the FEniCS tutorials are out of date and one should import the modules directly: import ufl, dijitso, FIAT, ffc This modified Dockerfile should illustrate this issue. |
For pip noobs (like me), the workaround is:
|
Another alternative is to do the following:
As far as I understand the broken |
Setting fenics as install requirement may break the installation (see #103). We therefore check whether fenics is installed and abort, if this is not the case.
Should not be |
Setting fenics as install requirement may break the installation (see #103). We therefore check whether FEniCS is installed and abort, if this is not the case. Co-authored-by: Frédéric Simonis <simonisfrederic@gmail.com>
Reopening this issue with the same rationale as for #154: Would be nice to avoid this problem trough technical means and a proper dependency handling. |
See https://fenicsproject.discourse.group/t/installing-python-package-with-fenics-dependency-breaks-fenics-installation/4476.
To me this looks like an upstream issue. The fenics adapter depends on fenics. Therefore the following dependencies in
setup.py
look correct:fenics-adapter/setup.py
Line 28 in fcd3f0c
However, if we assume a user has already fixed the FEniCS installation by manually uninstalling
fenics-ufl
, the fenics adapter will reinstallfenics-ufl
due to thefenics
dependency and (again) break the FEniCS installation. The user has to uninstallfenics-ufl
(again) after installing the fenics adapter.A possible solution that I have in mind is to declare FEniCS as a dependency of the adapter, but avoid reinstalling
fenics-ufl
. Is this possible?The text was updated successfully, but these errors were encountered: