JuliaDynamics/DrWatson.jl

Pkg.activate is not enough for forcing correct environment

Open

#245 opened on Apr 28, 2021

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Julia (94 forks)batch import
good first issue

Repository metrics

Stars
 (915 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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"

Contributor guide

Research direction
Inspect the issue example and understand how Julia's load path is affected by JULIA LOAD PATH. Determine the correct behavior and propose a fix to Pkg.activate to override the load path.
Tech stack
julia
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Julia
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65