-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Propagate package environment to local workers #43270
Conversation
8d93a56
to
8c2feee
Compare
8c2feee
to
d584ceb
Compare
d584ceb
to
0f17581
Compare
…ng#43270) Local workers now inherit the package environment of the main process, i.e. the active project, LOAD_PATH, and DEPOT_PATH. This behavior can be overridden by passing the new `env` keyword argument, or by passing `--project` in the `exeflags` keyword argument. Fixes JuliaLang#28781, and closes JuliaLang#42089.
…ng#43270) Local workers now inherit the package environment of the main process, i.e. the active project, LOAD_PATH, and DEPOT_PATH. This behavior can be overridden by passing the new `env` keyword argument, or by passing `--project` in the `exeflags` keyword argument. Fixes JuliaLang#28781, and closes JuliaLang#42089.
About the NEWS.md update, it looks like the ENV variables Tests on Julia 1.8LOAD_PATH
DEPOT_PATH
I believe this is because the entire julia> Distributed.remotecall_eval(Main, 2, :ENV) == ENV
true Perhaps the news entry can be reworded? The change is that the active project from the parent process is propagated, independently of how it was set (ENV variable, Suggested change: #48301 |
Propagate package environment to local workers, fixes #28781, closes #42089.