yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #14556
Re: Fixing the examples FEMxDEM
-
To:
yade-dev@xxxxxxxxxxxxxxxxxxx
-
From:
Janek Kozicki <janek_listy@xxxxx>
-
Date:
Sun, 27 Jan 2019 01:28:47 +0100
-
Face:
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUBAQEtLS1KSkpRUVFXV1dYWFhjY2Nzc3N3d3eHh4eKioqdnZ24uLjLy8vc3NxVIagyAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH2AIVEzgS1fgQtQAAAjRJREFUOMtt1DFv00AUAOAzFQNbjigSyoQaRaBMhKgLUyKXpVNNeUpk9vyDqFJhQ1kiBuaqAwJCqvPtSLY7RlTn5+5IdnYkkt/AOyfxXVLe5vf53Z1875kd34tOEax8djmj6GyjhB5bxz50GdsVZr9fqRjZwAtKOJw5Wqs2MMZ16ALHsaDncF7xAHix1oEFHAB8f+pRjcO4gfZDykcYzbiucRolOLUJ6kjA0xtVt+A6TySlM0RajIpK6DzwKZ/nOYbF/gclHMo1ZOHYY/+Ha+AWuM+3oMS4eeqYzZ8FiCltgUqI8cd2wwAVpJk+8LWYjBtnJdQpHQqJMd4Oxt4bU9ESiFGc5hkqaH74asAX4iabP5I5gZ+qjgGlJCqZa3h3lxhoeVcSE1qLQC4sqKOK9MGW9E3izFqqHokoztLFEgXg31sbZEKnWi2T74A4NxfVQqlkjKtcAWD+zcArFEES01dR0E/nnV0IgugmDd/2L84sOAouRBBHEc7gtc8teDkRlE0iNQPo2w3Xhh/D4TCIQ4LRLoTvgwjj6RRgavdurxYGMaIuGOyAW/PpNlCcU9/93AHenAWYjPoAwa+G3e3to/MgFNTAEKvKDjzuCzHTnY3qqdXtx24VijzQfZ0yewZ5cwRFQaa+mIYr1uI0I76+3W4xhlvoVRwOA0Fdl64HlJnxP6T8YpX/Lga4Wv4A3ErrU5oTfN7Mu/llXMl8RXEPji/lQkN3H7qXqgC2By47EXeU/7PJ/wPxRKMnuZwIeAAAAABJRU5ErkJggg==
-
In-reply-to:
<b54efc10-6231-5bf5-e5c7-901bf6a7baea@grenoble-inp.fr>
Bruno Chareyre said: (by the date of Thu, 24 Jan 2019 19:09:26 +0100)
> FEMxDEM: Ning Guo (if this adress does not work I know Ning has
> successors in HK)
I am trying to make it work. I found that
https://launchpad.net/escript-finley is probably inside package
python-escript.
I have compiled version python-escript_5.3-1_amd64.deb from source
and installed it, But still I have this error when starting the
FEMxDEM example:
from esys.escript import *
ImportError: No module named esys.escript
The strangest thing is that when I do:
grep esys.escript . -r --color
inside the source of package python-escript_5.3-1_amd64.deb I find
hundreds of lines that are doing this `from esys.escript import *`.
So I conclude that in yade it should work.
However my devuan ascii is based on debian stretch, so maybe some of
my packages are too old. I don't know which ones, though :( Or have a
bug regarding python detecting newly installed modules.
Maybe I should try this in devuan experimental, perhaps there it will
work.
Do you guys have any idea?
--
Janek Kozicki
Follow ups
References