JuliaDynamics/DrWatson.jl

Pkg.activate is not enough for forcing correct environment

Open

#245 创建于 2021年4月28日

在 GitHub 查看
 (6 评论) (0 反应) (0 负责人)Julia (915 star) (94 fork)batch import
good first issue

描述

This is perhaps a bit of a drive-by comment (I haven't used the package myself), and perhaps it has been discussed before but Pkg.activate is not enough to make sure you use the correct environment. Here is one example:

$ JULIA_LOAD_PATH=/tmp/Project.toml: julia --project=. -q
julia> Base.active_project()
"/tmp/tmp.ovN3Dd5eeE/Project.toml"

julia> Base.load_path()
4-element Vector{String}:
 "/tmp/Project.toml"
 "/tmp/tmp.ovN3Dd5eeE/Project.toml"
 "/home/fredrik/.julia/environments/v1.6/Project.toml"
 "/opt/julia/julia-1.6/share/julia/stdlib/v1.6"

贡献者指南

技术栈
无
领域
developer experiencetooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Julia basicsPkg.jlenvironment management
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Investigate the interaction between Pkg.activate and JULIA LOAD PATH. The issue shows that even after activating a project, the load path can be influenced by an external environment variable. Consider whether DrWatson should override the load path or issue a warning. Look at load path handling in DrWatson.jl source code and check for existing discussions or PRs. Implement a test that reproduces the scenario and propose a solution.