Use executable location as base for various file operations (#180) #185
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.
Currently, the FakeNet executable attempts to locate its files in the session's current working directory. However, this is not ideal as configuration files, for example, are actually located relative to the executable's location, not the location from which the user launched the executable. This issue was described in #180.
When inside a PyInstaller bundle, the parent directory of the executable can be retrieved using
os.path.dirname(sys.executable)
.I have applied this to various file operations throughout FakeNet. If I missed any, please let me know!