Closed aph3rson closed 2 weeks ago
This could be updated to default to something like os.path.dirname(os.path.realpath(__file__))
, which gets the directory of the current Python file.
Correct -- the default behaviour basically assumes the user double clicks the executable, the "running via absolute path on the command line" use case was not really considered 😅
Should be fixed by 078772ea33722672c7bad3fe30f7fb4753f3538d, released in v1.7.10.
Hephaistos specifies in its documentation that the binary must be placed within the Hades folder to run correctly.
This doesn't appear to be accurate - it seems that it's actually checking the current directory when running, and throwing an error if the current directory doesn't contain expected Hades files.
In this case, the binary is already in the right directory. It looks like it expects to be run as
./hephaistos
, rather than from any other working directory.Could the readme be updated accordingly? Alternatively, rather than default to checking
.
, check in the location the file is in?