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
In "ats/src/ats/executables.py" the import statement
from configuration import machine
is called from within the Executable class' init function.
This is a circular dependency workaround since
"configuration.py" imports "machines.py"
"machines.py" imports "configuration.py" (the contents of machines.py are not imported yet)
"configuration.py" imports "executables.py"
and "executables.py" imports "configuration.machine" (more accurately: from configuration import machine).
For now the code works since Executable (in executables.py) does not try to reference configuration.machine until after it has been imported elsewhere.
Goal
Resolve dependencies so "from configuration import machine" can exist outside of the Executable.init() call.
The text was updated successfully, but these errors were encountered:
Problem
In "ats/src/ats/executables.py" the import statement
is called from within the Executable class' init function.
This is a circular dependency workaround since
"configuration.py" imports "machines.py"
"machines.py" imports "configuration.py" (the contents of machines.py are not imported yet)
"configuration.py" imports "executables.py"
and "executables.py" imports "configuration.machine" (more accurately: from configuration import machine).
For now the code works since Executable (in executables.py) does not try to reference configuration.machine until after it has been imported elsewhere.
Goal
Resolve dependencies so "from configuration import machine" can exist outside of the Executable.init() call.
The text was updated successfully, but these errors were encountered: