New Python solve interface badly broken
Bug #888282 reported by
Garth Wells
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DOLFIN |
Fix Released
|
Critical
|
Anders Logg |
Bug Description
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_
in solving.py.
Changed in dolfin: | |
importance: | Undecided → Critical |
assignee: | nobody → Anders Logg (logg) |
milestone: | none → 1.0-rc1 |
Changed in dolfin: | |
status: | New → Confirmed |
Changed in dolfin: | |
status: | Confirmed → Fix Committed |
Changed in dolfin: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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: bcs(args[ 2])
> 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_
>
> in solving.py.
>
> ** Affects: dolfin
> Importance: Critical
> Assignee: Anders Logg (logg)
> Status: New