yzhao062 / pyod / 25819303985

94%

master: 94%

push

github

fix(gaal): extend optional-torch guard to mo_gaal, so_gaal, so_gaal_new

Follow-up to PR #660. PR #660 fixed pyod/models/gaal_base.py's
print-then-crash torch import pattern, but the user-visible imports
`from pyod.models.mo_gaal import MO_GAAL` and
`from pyod.models.so_gaal import SO_GAAL` reach the old broken pattern
in their OWN module tops before importing from gaal_base, so without
torch installed users still got the bare `ModuleNotFoundError`.
Apply the same try/except guarded-import pattern to mo_gaal.py,
so_gaal.py, and so_gaal_new.py (the v3+ deep-learning re-implementation
of SO_GAAL also tracked in the GAAL family). All four files now raise
the identical actionable message pointing at
`pip install pyod[torch]` or `pip install torch`. Also unifies the
gaal_base.py message to mention the project-native extra alongside
the raw torch install command.

Verified with a missing-torch import blocker: pyod.models.gaal_base,
pyod.models.mo_gaal, pyod.models.so_gaal, and pyod.models.so_gaal_new
all raise the new actionable ImportError. GAAL tests
(test_mo_gaal.py + test_so_gaal.py + test_so_gaal_new.py) pass 44/44
in the torch-installed environment.

Note: a regression test that runs in a torch-installed environment but
exercises the missing-torch import path is left for a separate
follow-up; the import-blocker test scaffolding is nontrivial relative
to this small bug fix.

8 of 15 new or added lines in 4 files covered. (53.33%)

17901 of 19094 relevant lines covered (93.75%)

4.67 hits per line