Occasionally imports into __init__.py files (e.g., in dingo.core.utils) result in circular import errors when modules being imported refer to each other via __init__.py. To fix this, for imports within dingo, import submodules directly, i.e., use
from dingo.core.utils.dataset_utils import build_train_and_test_loaders
rather than
from dingo.core.utils import build_train_and_test_loaders
The latter is convenient for external use, but internally it is best to use the full path.
Occasionally imports into
__init__.pyfiles (e.g., indingo.core.utils) result in circular import errors when modules being imported refer to each other via__init__.py. To fix this, for imports within dingo, import submodules directly, i.e., userather than
The latter is convenient for external use, but internally it is best to use the full path.