Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The ~ in a path should be replaced by the home directory #234

Closed
smarr opened this issue Feb 3, 2024 · 1 comment
Closed

The ~ in a path should be replaced by the home directory #234

smarr opened this issue Feb 3, 2024 · 1 comment
Labels

Comments

@smarr
Copy link
Owner

smarr commented Feb 3, 2024

Currently, I think we can't use ~ in a path, as one normally can in a shell.
This means many paths need to be fully qualified, which binds a conf file to a very specific setup.

The problem is, we don't want expand the ~ too early and in the wrong place either, because then we end up with RunId objects not being the same anymore for the same path.
So, we could not compare across different machines. Generally, comparing between machines is done very rarely because it's not generally useful, but sometimes, we are indeed interested in the machines.

So, a good point for the expansion might be here:

def cmdline_for_next_invocation(self):

This bit was added allow iterations to be part of the command line, also with the goal to avoid breaking the RunId identity: #216

@smarr
Copy link
Owner Author

smarr commented Jul 5, 2024

Resolved with #240.

@smarr smarr closed this as completed Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

1 participant