You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to write unit tests for your models under Python 3.8, when importing the pip-installed mllaunchpad packages, it might appear as if its submodules (like mllaunchpad.datasources, mllaunchpad.resource) are not always accessible ("... has no submodule ..."). But sometimes they are! It might even make a difference when I (re)import mllaunchpad.
BUT: This might just be due to the difference between attributes and imports in Python. Submodules don't appear to be available immediately as mllaunchpad.submodule, but through import submodule from mllaunchpad.
Description
When trying to write unit tests for your models under Python 3.8, when importing the pip-installed mllaunchpad packages, it might appear as if its submodules (like
mllaunchpad.datasources
,mllaunchpad.resource
) are not always accessible ("... has no submodule ..."). But sometimes they are! It might even make a difference when I (re)import mllaunchpad.BUT: This might just be due to the difference between attributes and imports in Python. Submodules don't appear to be available immediately as
mllaunchpad.submodule
, but throughimport submodule from mllaunchpad
.So if
does not work, try
Steps to reproduce
The text was updated successfully, but these errors were encountered: