Skip to content

Conversation

@ven-k
Copy link
Member

@ven-k ven-k commented Mar 1, 2024

Similar to Julia's command line argument --project,

This also changes how Pkg.activate behaves wrt temp (disallows) and stdlib (activates @stdlib/Project.toml)

Related to these, the PR adds tests and updates docs.

ven-k added 4 commits March 1, 2024 15:24
Similar to Julia's command line argument `--project`,
- `activate @temp` activates temp environment
- `activate @stdlib` activates `Sys.STDLIB`
- `activate @.` activates current project
- `activate @` activates active project
Julia's CLI arg `--project=@temp` now creates temporary environments. So, with a helpful error message, indicate that naming shared environment as `temp` is not allowed.
Julia CLI arg `--project=@stdlib` activates STDLIB project; match the
behavior here.
@ven-k
Copy link
Member Author

ven-k commented Mar 1, 2024

While here, I wonder if this part of load_path_expand in initdefs.jl of Julialang/julia should be separated out as an internal function which Pkg can then use in parse_activate and activate (for shared = <> dispatch).
This would keep the behavior in sync.

@ven-k ven-k requested a review from KristofferC March 8, 2024 07:29
@github-project-automation github-project-automation bot moved this to New in Pkg.jl Jul 2, 2025
@IanButterworth
Copy link
Member

I don't understand the need for this as we have activate --temp, activate . etc.

Please feel free to clarify/disagree if I'm being shortsighted.

@github-project-automation github-project-automation bot moved this from New to Done in Pkg.jl Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants