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

Behavior of no-arg activate with julia --project changed with julia v1.6 #3084

Open
stemann opened this issue May 16, 2022 · 1 comment
Open

Comments

@stemann
Copy link

stemann commented May 16, 2022

Did the behavior of no-arg Pkg.activate() change with Julia v1.6, such that it activates the default env.?

In other words - does the docs need updating, cf. https://pkgdocs.julialang.org/v1/api/#Pkg.activate ?

On Julia v1.5, julia --project --eval 'using Pkg; Pkg.activate(), the local project is activated:

$ docker run -it --rm julia:1.5 bash -c "julia --eval 'using InteractiveUtils; versioninfo(); using Pkg; Pkg.activate(); Pkg.generate(\"Foo\")'; cd Foo; julia --project --eval 'using Pkg; Pkg.activate(); Pkg.activate(\".\")'"
Julia Version 1.5.4
Commit 69fcb5745b (2021-03-11 19:13 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-9.0.1 (ORCJIT, skylake)
Environment:
  JULIA_GPG = 3673DF529D9049477F76B37566E3C7DC03D6E495
  JULIA_VERSION = 1.5.4
  JULIA_PATH = /usr/local/julia
 Activating environment at `~/.julia/environments/v1.5/Project.toml`
 Generating  project Foo:
    Foo/Project.toml
    Foo/src/Foo.jl
 Activating environment at `/Foo/Project.toml`
 Activating environment at `/Foo/Project.toml`

On Julia v1.6-v1.7, julia --project --eval 'using Pkg; Pkg.activate(), activates the default env.:
v1.6

$ docker run -it --rm julia:1.6 bash -c "julia --eval 'using InteractiveUtils; versioninfo(); using Pkg; Pkg.activate(); Pkg.generate(\"Foo\")'; cd Foo; julia --project --eval 'using Pkg; Pkg.activate(); Pkg.activate(\".\")'"
Julia Version 1.6.6
Commit b8708f954a (2022-03-28 07:17 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-11.0.1 (ORCJIT, skylake)
Environment:
  JULIA_GPG = 3673DF529D9049477F76B37566E3C7DC03D6E495
  JULIA_VERSION = 1.6.6
  JULIA_PATH = /usr/local/julia
  Activating environment at `~/.julia/environments/v1.6/Project.toml`
  Generating  project Foo:
    Foo/Project.toml
    Foo/src/Foo.jl
  Activating environment at `~/.julia/environments/v1.6/Project.toml`
  Activating environment at `/Foo/Project.toml`

v1.7

$ docker run -it --rm julia:1.7 bash -c "julia --eval 'using InteractiveUtils; versioninfo(); using Pkg; Pkg.activate(); Pkg.generate(\"Foo\")'; cd Foo; julia --project --eval 'using Pkg; Pkg.activate(); Pkg.activate(\".\")'"
Julia Version 1.7.2
Commit bf53498635 (2022-02-06 15:21 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-12.0.1 (ORCJIT, skylake)
Environment:
  JULIA_GPG = 3673DF529D9049477F76B37566E3C7DC03D6E495
  JULIA_VERSION = 1.7.2
  JULIA_PATH = /usr/local/julia
  Activating project at `~/.julia/environments/v1.7`
  Generating  project Foo:
    Foo/Project.toml
    Foo/src/Foo.jl
  Activating project at `~/.julia/environments/v1.7`
  Activating project at `/Foo`
@KristofferC
Copy link
Sponsor Member

My guess is this got changed based on JuliaLang/julia#36434. If the docs are out of date, then they do need updating, indeed.

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

2 participants