← Back to team overview

dolfin team mailing list archive

Re: Viper update broke DOLFIN

 

On Tue, Mar 25, 2008 at 05:52:38PM +0100, Ola Skavhaug wrote:
> Anders Logg skrev den 25/03-2008 følgende:
> > It looks like some recent updates to Viper (blame: Martin :-) has
> > broken the Function class in DOLFIN.
> 
> Change line 2 in site-packages/dolfin/plot.py to the following:
> from viper.viper_dolfin import Viper, plot, update, interactive, save_plot

Thanks, this works fine.

> That is a good fix, avoiding wildcard import at library level.

Yes, definitely. Any suggestions are welcome.

-- 
Anders



> Ola
>  
> > Here's what I get when running the standard Poisson demo in DOLFIN:
> > 
> > Traceback (most recent call last):
> >   File "demo.py", line 53, in <module>
> >     f = Source(element, mesh)
> >   File "demo.py", line 29, in __init__
> >     Function.__init__(self, element, mesh)
> >   File
> >   "/home/logg/local/lib/python2.5/site-packages/dolfin/dolfin.py",
> >   line 3722, in __init__
> >     this = _dolfin.new_cpp_Function(*args)
> > NotImplementedError: Wrong number of arguments for overloaded function
> > 'new_cpp_Function'.
> > 
> > It looks like (Py)DOLFIN now believes that Function is the wrapped
> > dolfin::Function and not dolfin.Function defined in assemble.py.
> > 
> > Any ideas what goes wrong?
> > 
> > It's possible that we just need to make a simple rearrangement of the
> > order of imports.
> > 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev


References