Allow to manually specify the backend for an analysis #5
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.
Currently, the backend is determined in every analysis using
get_backend
, so analyses will always be executed in the default backend. Although this will not occur very often, this makes it difficult to run multiple backends side-by-side. This PR adds abackend
parameter to each analysis. By default, thevisisipy.analysis.base.analysis
decorator will automatically supply the configured backend, but if a different backend is used instead, this backend will be used by the analysis.Furthermore, instead of forcing
return_raw_result
to be the last parameter,return_raw_result
andbackend
are now forced to be keyword-only parameters.