Prevent the Settings object from pointing to two separate things

We need to do this dance because shared.py reassigns the global Settings
object to point to a new class, but because Python is lexically scoped,
the Settings global name in tests/runner.py would not get updated to
point to the new name, which would cause changes to Settings.FOO_BAR in
runner.py not be reflected in Settings.serialize() and therefore not
being passed down to emcc.

0 files changed, 0 insertions, 0 deletions