Great, adding "dolfin.cpp." to the imports in the swig file generation
worked fine. But the new and better import doesn't work:
/home/martinal/opt/fenics/dorsal-unstable-py3/lib/python3.4/site-packages/dolfin/cpp/la.py
in ()
110 has_petsc4py = _la.has_petsc4py
111 import dolfin.cpp.common
On Fri, Aug 1, 2014 at 1:35 PM, Martin Sandve Alnæs
wrote:
> It doesn't make sense that _swig_property() triggers
> Parameters.__setitem__ so something fishy is going on.
>
> If we disable this line in common.py the error disappears:
> #parameters = _common.get_global_parameters()
>
Probably no
It doesn't make sense that _swig_property() triggers Parameters.__setitem__
so something fishy is going on.
If we disable this line in common.py the error disappears:
#parameters = _common.get_global_parameters()
Then we get to this error instead:
/home/martinal/opt/fenics/dorsal-unstable-py3/l
It looks like line 2473 triggers a call to __setitem__, which is strange
in it self as it was not done in py2. That call goes into our swig extended
python code which calls _get_parameter_keys. That call triggers a type
miss-match for its self argument. This occurs for example when a class that
ar
Note that you need the next branches of instant, fiat, ffc and master
branch of ufl to test Aslaks dolfin branch.
I don't understand what's happening here, this is swig-generated code which
fails to match the python Parameters object with the C++ Parameters type.
Martin
On 1 August 2014 10:24,
I'm trying to get dolfin to run with python 3. Previously this summer I
have changed ffc, fiat, instant and ufl, which are now included in the
master/next branches.
Dolfin now builds for python 2 and 3, but for python 3 it fails to import
from dolfin. You can find my code her:
https://bitbucket.or
