Julia: Difference between revisions

Alternatively, one can create a [[Singularity]] image with a chosen version of Julia and a selection of packages, and JULIA_DEPOT_PATH redirected inside the container. This does mean that you lose the advantage of the Compute Canada optimized Julia modules. However, your container now contains the potentially very large set of small files inside 1 container file (.sif), potentially improving IO performance. Reproducibility is also improved, the container will run anywhere as-is. Another use case is if you want to test Julia nightly without altering your local Julia installation, or when you need to bundle your own specific dependencies, because the container creation gives you complete control at creation.

Note that if you do not create a virtual environment as shown above, PyCall will default to the operating system python installation, which is never what you want. It will invoke Conda.jl, but fail to recognize the correct path unless you rebuild with ENV["PYTHON"]="". In addition, apart from incompatibilities with the software stack, the Miniconda installer creates a large number of files inside <code>JULIA_DEPOT_PATH</code>. If that is <code>~/.julia</code>, the default, you can run into performance and quota issues.