- changed status to resolved
Deprecation: remove AssemblerBase::reset_sparsity prior to 1.5 release.
AssemblerBase::reset_sparsity
is going to be deprecated in 1.4 release and should be removed after 1.4 release. Probably also deprecated_bool
class should be removed. Affected files:
grep -r reset_sparsity dolfin/ site-packages/ demo/ test/
grep -r bool_deprecated dolfin/ site-packages/ demo/ test/
dolfin/swig/fem/pre.i
dolfin/swig/fem/post.i
dolfin/fem/AssemblerBase.h
site-packages/dolfin/fem/assembling.py
Comments (11)
-
-
reporter - changed status to open
-
You forgot
assembling.py
. -
What about
bool_deprecated
inAssemblerBase.h
? Shouldn't we remove this also?
-
Please don't touch assembling.py, I'm handling that.
-
@blechta I fixed assembler.py in another branch (by accident).
We need to coordinate the removal of deprecated functions better. I started branches for some functions before the release (so I could merge into development branches that would not be merged into master before 1.4). Cleaning this all up with multiple developers making the same changes will be a pain.
-
Removal of the deprecated arguments other than reset_sparsity in assembler.py needs to be done in concert with a bunch of other issues in the ufl/dolfin intersection that I've been alone at handling. If you only removed reset_sparsity that's an easy merge.
-
@martinal I'm happy for you to take care of it.
You haven't all on your own. See https://bitbucket.org/fenics-project/dolfin/branch/garth/test-updates-for-interface-changes.
-
reset_sparsity in assembling.py is removed in master now. Can we close this now?
-
reporter What about removing illogically placed
AssemblerBase.h/bool_deprecated
class. It can be anytime recovered when needed... -
reporter Fix in
fix-issue-285
branch. Please, merge. -
reporter - changed status to resolved
Both
reset_sparsity
andbool_deprecated
are already removed. -
- removed milestone
Removing milestone: 1.5 (automated comment)
- Log in to comment
Fixes Issue
#285.→ <<cset 21a6fc735f98>>