I admit that the following problem might arise only because my team is mixing two concepts–Package and Application–in a single Project. Still, let me pose the problem: I have a package “Pope” that serves mainly as a library of analysis tools (for superconducting x-ray microcalorimeter data) but als…

You can just make a regular old temporary directory to put your environment in. One of Pkg’s many strengths is that it separates the set of installed packages from the active environment. This means creating new environments is virtually free! You can think of Pkg.add as “make sure these packages a…

Both of these solutions print out a lot of unwanted text… for example @00vareladavid ’s solution on my computers starts by outputting: >julijulia oneilg$ julia script.jl Updating registry at `~/.julia/registries/General` Updating git-repo `https://github.com/JuliaRegistries/General.git` Updati…

Not on the official binaries yet, but https://github.com/JuliaLang/Pkg.jl/pull/1053 just merged a few days ago. In the near future you will be able to do Pkg.add("Example"; io=io) to capture all Pkg output.

I notice you’re the author of the PR, so thanks. I can’t tell from the PR, will Pkg.activate("ABC"; io=io) work as well?

Sure! It should work for all Pkg API commands.

Thanks for the tips on the behavior of new Pkg. It has been difficult for me to make sense of the many changes, particularly the changes in philosophy, but I am getting there. I like your temporary directory solution, and I will use it with or without the extra output. I’ll also look forward to the…

One extra note: @00vareladavid didn’t know this, butPope.jl happens to be a “local project”: it’s not in the main Julia Registry. That means that the tempdir solution will not work in this specific case, because Pkg doesn’t know how to find my project. We would need to add our local registry with Pk…

Thanks @hendri54 . And I should point out that @ggggggggg is my Julia-using partner. He used this very guide (and your help here on Discourse) to get our private registry going. I think he and I could make point 3 work. Or at least, he could. If choosing between idea 1 and 2, I guess the key questi…

I usually have a script header like this #!/bin/bash #= JULIA="${JULIA:-julia}" JULIA_CMD="${JULIA_CMD:-$JULIA --color=yes --startup-file=no}" export JULIA_PROJECT="$(dirname ${BASH_SOURCE[0]})" export JULIA_LOAD_PATH=@:@stdlib # exclude default environment exec $JULIA_CMD -e 'include(popfirst!(AR…

[image] tkf: JULIA_LOAD_PATH=@:@stdlib is important if you want to avoid accidentally relying on your default environment. You might even consider leaving out stdlib here.

How to activate a package in a script?

General Usage

hendri54 August 30, 2019, 7:32pm 9

On point 3 (custom registry), see Creating a custom registry. One of the contributors has worked out a step by step guide.

Topic		Replies	Views
How does one activate the environment of an added package? General Usage package	3	542	October 5, 2019
How to run a Julia script from the command line which has package dependencies? New to Julia	4	477	October 2, 2024
How to install package dependencies for unregistered package General Usage packages	20	6040	March 18, 2020
Workflow to develop standalone scripts that depend on both standard and custom Packages General Usage	8	599	January 25, 2021
Distributing scripts with self-managed dependencies Package Management	12	981	August 1, 2023

How to activate a package in a script?

Related topics