Use importlib.util.find_spec
to check if lm_eval
is installed instead of trying to import it
#1023
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.
There is a circular dependency when trying to import
lm_eval
insidetorchao
. The chain is like this:torchao -> lm_eval -> transformers.pipelines -> torchao
And results in the following error:
which
_lm_eval_available
to be erroneously set toFalse
, even iflm_eval
is availablelm_eval's
initialization, leaving it partially initializedyou can observe this with:
Having a bare except clause here was suppressing this circular import error, which from glancing around seems kind of like a general pattern in this code base. It might be worth reconsidering this pattern.