I did come across with the dependency hell for a Pyton script I wrote 4-5 years ago whose output was finally to get published. I need to run however my script under a slightly changed scenario and when I try to blindly press run on each cell of a Python notebook… BOOM !! I come to the problem of de…

[image] sylvaticus: Which is the proper way to “ship” a project (that can be a simple script) with the exact version of its dependencies ? ]activate . on the folder , ].add the various dependencies and then ship the folder with the script and the two files Project.toml and Manifest.toml ? Yes…

[image] GunnarFarneback: You need to be observant that you don’t depend on anything in your global environment though, preferably by removing it from your load path. How do I do that (be sure that if I use some package that’s has been included in the local Project/Manifest file) ?

See How to install packages which are needed only for development - #2 by fredrikekre for a related discussion. In contrast to that case you most likely want to keep @stdlib though.

I see. It would have been nice if there was a way to “force” it from Julia itself rather than using env variables, something like Pkg.envpaths(["."])

Haha, seems I got lost in my searches. That was what I had intended to link to.

I think I finally got it. for example on a project where I need DataFrames: Only once: cd(@__DIR__) using Pkg Pkg.activate(".") Pkg.add("DataFrames") # .. add the other package needed... In myProject.jl # This script works on julia 1.5 cd(@__DIR__) using Pkg push!(empty!(LOAD_PATH), ".") Pkg.ac…

Looks about right to me! [image] sylvaticus: Only once: cd(@__DIR__) using Pkg Pkg.activate(".") Pkg.add("DataFrames") # .. add the other package needed... You can also just use the package REPL mode (type ] to enter the mode, then add DataFrames etc), instead of a separate script. [ima…

correct, edited my post above…

[image] sylvaticus: And what if the machine has a newer version of Julia? I did notice that both Project.toml and Manifest.toml do not contain any information on the Julia base version. You can (and should) include a [compat] entry for julia, too.

To add on to what @Tamas_Papp wrote, you can find the documentation about compatibility in the docs of Pkg (linked from the documentation of julia).

How to ship the exact environment together with a julia script

General Usage

ericphanson October 12, 2020, 10:29am 6

You can do it from within Julia, you just manipulate the global variable LOAD_PATH. See e.g. Creating empty isolated environment - #5 by fredrikekre

Topic		Replies	Views
Correct way to prepare dependencies of a julia project for publishing? General Usage question	9	3197	February 28, 2022
Julia package versioning is a real nightmare to me. What am I doing wrong? General Usage package , versions	17	1190	January 21, 2025
Best practice for academic code reproducibility (Manifest.toml between versions of julia) Package Management reproducibility	6	1239	March 23, 2022
A slight flaw in the Project/Manifest/Env logic? General Usage	7	667	June 14, 2020
Managing dependencies in packages General Usage	1	363	February 12, 2020

How to ship the exact environment together with a julia script

Related topics