← Back to team overview

dolfin team mailing list archive

Re: FunctionSpace error in python

 

On Thursday 22 January 2009 17:02:41 A Navaei wrote:
> Johan,
>
> Thanks, instant-clean did the trick! Maybe this should be somehow
> automated.

Yes, I have thought about it.

Is it possible to add a call to instant-clean in the install script of the ffc 
and dolfin packages Johannes?

We could(should!) also add the swig version in the instant signature in both 
ffc and dolfin, because this it probably what caused the problem for Ali, and 
all the others that upgrade.

Johan

>
>
> -Ali
>
> 2009/1/22 Johan Hake <hake@xxxxxxxxx>:
> > On Thursday 22 January 2009 16:29:58 A Navaei wrote:
> >> Hi,
> >>
> >> Since updating to 0.9.0-1+intrepid1, when calling FunctionSpace in
> >> python, I receive the following error generated by swig python
> >> wrapper:
> >>
> >> Traceback (most recent call last):
> >>   File "../tests/test04.py", line 15, in <module>
> >>     V = FunctionSpace(mesh, "CG", 1)
> >>   File "/usr/lib/python2.5/site-packages/dolfin/functionspace.py",
> >> line 183, in __init__
> >>     FunctionSpaceBase.__init__(self, mesh, element)
> >>   File "/usr/lib/python2.5/site-packages/dolfin/functionspace.py",
> >> line 48, in __init__
> >>     self.__dolfin_element = cpp.FiniteElement(self.__ufc_element)
> >>   File "/usr/lib/python2.5/site-packages/dolfin/cpp.py", line 9755, in
> >> __init__ this = _cpp.new_FiniteElement(*args)
> >> TypeError: in method 'new_FiniteElement', argument 1 of type
> >> 'std::string'
> >>
> >> Clean re-installation did hot help this. Any idea what could be wrong?
> >
> > also...
> >
> > Have you made an instant-clean?
> >
> > Johan




Follow ups

References