I recently learned about “shared environments”, aka the default v1.3 environment. It’s quite a revelation, but I don’t understand how it works. Suppose I have Package A which depends on B@v1.0.0, and is compatible with no other version of B. A is in the shared environment’s Project.toml. Environme…

[image] cstjean: does using A fail right away, With fail I just meant that package A might not work correctly because an incompatible version of B is loaded. Again, compat information does not influence what package is being loaded at all.

I think you will find this useful: [image] Handling various types of dependencies General Usage I think you can find an answer in this comparison of Julia’s Pkg to Go’s packaging system: Go is treating packages with different major versions as essentially different pac…

Compat has nothing to do with what is being loaded. Compat is used by the resolver when the Manifest is created but nothing in the code that loads packages looks at it. Given a package to be loaded, each Manifest in Base.load_path() is looked at and the version that is first found is loaded. So her…

E requires C, which is only compatible with B@v2.0.0, so that would be loaded? Then how can using A succeed, if it’s only compatible with B@v1.0.0? In other words, I always assumed that you can’t combine/stack environments, because the manifest of environment 1 and environment 2 can be incompatible…

[image] cstjean: E requires C , which is only compatible with B@v2.0.0 , so that would be loaded? Then how can using A succeed, if it’s only compatible with B@v1.0.0 ? It might fail. [image] cstjean: Or are two different versions of A loaded simultaneously? No, only one version of eac…

[image] kristoffer.carlsson: It might fail. Ok, so if A is currently at v1.3.0 in the shared environment (unpinned), incompatible with the B version in the E manifest, does using A fail right away, or does julia look for another version of A compatible with the B from E?

Oh, makes sense! Sorry for being obtuse above, and thank you for the patient answers.

Shared environments

General Usage

hendri54 March 15, 2020, 12:22pm 2

I think you will find this useful:

Import the same package after activating new environment

Topic		Replies	Views
Creating an environment to use specific versions of packages, Julia uses most current anyway General Usage	2	1093	April 22, 2020
Ignore package version compat New to Julia pkg	2	1071	April 11, 2021
Clarifying package compatibility rules General Usage	1	369	October 26, 2019
[ANN] ShareAdd.jl - making easy to import packages from multiple environments Package Announcements package , announcement , workflow , shared-environments , stacked-environments	17	1241	April 13, 2026
Shared and stacked environments General Usage workflow , shared-environments , stacked-environments	3	276	October 13, 2024

Shared environments

Related topics