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

Allow @everywhere include(...) to override default path behavior #84

Open
dlakelan opened this issue Sep 13, 2022 · 0 comments
Open

Allow @everywhere include(...) to override default path behavior #84

dlakelan opened this issue Sep 13, 2022 · 0 comments

Comments

@dlakelan
Copy link

According to tests and the documentation string:

  Similar to calling remotecall_eval(Main, procs, expr), but with two extra
  features:

  - `using` and `import` statements run on the calling process first, to ensure
    packages are precompiled.
  - The current source file path used by `include` is propagated to other processes.

This last "feature" overrides the path even if that isn't desired behavior. I discovered this when doing

@everywhere include("./utilities.jl")

and I expected it to read from the "current directory" that the remote julia process started in, but in fact it tried to read from my home directory (same directory as on my machine where the whole process was initiated) however that path doesn't exist remotely and isn't the desired behavior. It would be nice to have an option to not have @everywhere include(...) override the path.

@dlakelan dlakelan changed the title Allow @everywhere include(...) to override path Allow @everywhere include(...) to override default path behavior Sep 13, 2022
@vtjnash vtjnash transferred this issue from JuliaLang/julia Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant