Skip to content

Relative pathing is impractical #3

@TheEimer

Description

@TheEimer

Unfortunately for external usability, this repo relies a lot on relative pathing. If I just want to use the benchmark as a submodule for a different project I first need to manually add the directory to my path since it's not an installable package. Then I need to switch the data path since that is hardcoded to be relative for some reason.

Suggested improvements:

  • Make the repo an installable package to make it importable
  • Instead of reading from a relative path, hardcode the default to be absolute (can be done e.g. by using Path(file).resolve().parent as a base path). Then the directory from the repo will always be the default independent of the execution location

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions