Suppose one is getting started with Julia, but has made a series of scripts to pass on to someone else, that has just installed julia for the first time on its machine. Without having to specify which Packages are to be used to make your scripts work, and without say to him nothing on packages he s…

@Tamas_Papp , Can you clarify how this would work without git? Let’s say you share with them a dropbox folder (I know, I know) or email them a .zip file.

Unzip the zip file. Start julia with julia --project=/path/to/unzipped/folder or just cd to the folder and start with --project, run import Pkg; Pkg.instantiate(). Done.

If you really want to have the script automatically install dependencies, you can do something like the following at the top of your script: try @eval using MyDependency catch @warn "Unable to import MyDependency. Instantiating project." Pkg.instantiate() @eval using MyDependency en…

This will break if there is an incompatible version of MyDependency that happens to be available. If someone insists on a single, self-contained script, it could call Pkg.instantiate() every time it is run. This is a small overhead, but may be acceptable in some contexts. The alternative is …

It would have to be a pretty long-running script for Pkg.instantiate to be small overhead unfortunately. julia> @time Pkg.instantiate() 7.608510 seconds (12.10 M allocations: 566.187 MiB, 5.94% gc time) But you’ve still convinced me that try-wrapped using is highly brittle rather than “somewhat”…

Try running it for the second time, it should be much faster. That said, this is not something I would do. The key problem is that “standalone scripts” are not really a meaningful concept in Julia, as extra information is needed to resolve “simple” code loading like using SomePackage Depending on…

[image] Tamas_Papp: Try running it for the second time, it should be much faster. The 7.6 seconds was the second time running it (in a fresh Julia session).

Pkg.instantiate() tends to be slow on Windows. Probably due to the antivirus’ intrusive snooping in all the git files behind the scenes.

I would put your code, the Project.toml, and the Manifest.toml in a zip file, send it to your friend, and make sure your “main.jl” script begins with (only on 1.3 does this code work) using Pkg pkg"activate ." pkg"instantiate" I give some examples of this in a blog post here A Newcomers Guide To …

Distributing own julia scripts

New to Julia

Tamas_Papp February 13, 2020, 3:50pm 19

Please look at the docs and earlier discussions, eg

https://julialang.github.io/Pkg.jl/v1/registries/

Topic		Replies	Views
Distributing scripts with self-managed dependencies Package Management	12	988	August 1, 2023
How to install package dependencies for unregistered package General Usage packages	20	6061	March 18, 2020
Workflow to develop standalone scripts that depend on both standard and custom Packages General Usage	8	603	January 25, 2021
How to run a Julia script from the command line which has package dependencies? New to Julia	4	488	October 2, 2024
Installing packages from a list New to Julia	3	1093	February 4, 2019

Distributing own julia scripts

Related topics