Resolve NameError when implementing satellite killer #944
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.
A silly bug has slipped through the cracks!
When running satellite killer outwith Beersheba it behaves normally, but when trying to run it from the command line as
city Beersheba Beersheba_satkill.confyou receive this error message:Naively importing
CutTypedoes not resolve this issue. The problem appears to be due to theglobals_used withinexec()not including CutType, but rather just the built-in imports (& numpy).I believe the Beersheba test doesn't capture this issue as it never uses
configure()fromconfigure.py, and as such never follows through the Traceback shown above.This PR resolves this issue by including
CutTypeinto the dictionary of 'built-in' modules, but I believe this issue should be addressed more fully (perhaps an improvement in the output error ofread_included_file()if the module isn't included in thebuiltins)