dolfin team mailing list archive

Thread
Date

Re: [Bug 888282] [NEW] New Python solve interface badly broken

To: Launchpad Bug Tracker <888282@xxxxxxxxxxxxxxxxxx>
From: Anders Logg <logg@xxxxxxxxx>
Date: Wed, 9 Nov 2011 22:10:27 +0100
Cc: DOLFIN Mailing List <dolfin@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <20111109205256.7836.87009.launchpad@chaenomeles.canonical.com>
User-agent: Mutt/1.5.21 (2010-09-15)

Looks like confusion about whether bcs should be a keyword argument or
not. Should we support both this

  solve(a == L, Uh, bcs=bcs)

and this

  solve(a == L, Uh, bcs)

?

--
Anders


On Wed, Nov 09, 2011 at 08:52:56PM -0000, Launchpad Bug Tracker wrote:
> Garth Wells (garth-wells) has assigned this bug to you for DOLFIN:
>
> New solve interface for variational problem has a serious bug. The code
>
>     solve(a == L, Uh, bcs=bcs)
>
> does not work. Culprit looks like
>
>     # Extract boundary conditions
>     if len(args) == 2:
>         bcs = []
>     else:
>         bcs = _extract_bcs(args[2])
>
> in solving.py.
>
> ** Affects: dolfin
>      Importance: Critical
>      Assignee: Anders Logg (logg)
>          Status: New