Remove watertap from required dependencies #9
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.
parameter_sweep._compat
so thatget_solver()
(from IDAES) is available even ifwatertap
is notimport watertap
after the IDAESget_solver()
importwatertap
was available, but didn't have its ownget_solver()
implementationidaes
, but notwatertap
, could be importedwatertap.core.solvers
exists: useget_solver()
from WaterTAPwatertap
is not available, but IDAES is: useget_solver()
from IDAESwatertap
is available, but doesn't have its ownget_solver()
(i.e. WaterTAP version preceeding Implementget_solver
for WaterTAP watertap#1353): useget_solver()
from IDAES, counting on the fact that the client code will importwatertap
, and therefore the global implicit WaterTAP solver settings will be applied to the solver returned by IDAES'sget_solver()
pytest.importorskip()
for tests that use otherwatertap
imports