Fix import paths in simulation
module
#838
Merged
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.
Prior to 93af28, the
simulation
directory was added toPYTHONPATH
by appending tosys.path
at the start of each file, before submodules ofsimulation
such ascore
andinterfaces
were imported.In 93af28, the calls to
sys.path.append
were moved below the import block and so relative imports ofcore
andinterfaces
no longer resolve and the simulator fails to start with errors such as:This commit prefixes the submodule imports with
simulation.
so the imports can be resolved, and without needing to manipulatesys.path
. This works even when running the simulator outside the source repository, assetuptools.find_packages
is used insetup.py
to find the modules to package, and this finds thesimulation
module.