BUG: random_walker: fix import path for umfpack #5090
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
random_walker
seems to have a code path to allow use of UMFPACK, but it does not seem to get used even ifscikit-umfpack
is installed. The issue seems to be that theumfpack
module is not visible viascipy.sparse.linalg.dsolve
, but only within thescipy.sparse.linalg.dsolve.linsolve
submodule. As far as I could tell, it has been this way in SciPy for many years. I verified locally that the tests still pass whenscikit-umfpack
is installed and added a new import test, although I don't think we ever run withscikit-umfpack
on CI currently.I thought about adding
scikit-umfpack
torequirements/optional.txt
, but it does not have wheels on PyPI for recent Python or for Windows, so I have left it out for now.Checklist
./doc/examples
(new features only)./benchmarks
, if your changes aren't covered by anexisting benchmark
For reviewers
later.
__init__.py
.doc/release/release_dev.rst
.