Import gclib relative to wwrando.py instead of current working directory #368
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.
Executing the randomizer from source currently only works when the working directory is the root of the repository, with gclib being loaded from a path relative to the working directory of the shell. This changes the gclib load path to be relative to the
wwrando.py
file so that it's possible to execute the randomizer from different directories.A similar method is already used in the assemble.py script here:
wwrando/asm/assemble.py
Lines 14 to 16 in ccb32a3
This might be linux-only (not sure how cwd works on other OS), and only shows up when running from source rather than release binaries (I tested that this change doesn't break a (linux) release binary though), so this is mostly for convenience when developing, but it would also be useful for the racetime.gg bot which can run multiple versions of the randomizer side-by-side
For example, on master when running from one directory up the tree it fails like this: