has been driving me nuts for a while now. For instance, on mybinder. Is the end of the divergence nigh?
Are you talking about the manifest file of an environment? Generally speaking, don’t assume a manifest generated with julia v1.x can be instantiated with julia v1.y, with x != y. This principle has always been true since v1.0, even though some minor versions may have been compatible between each other.
In particular, it is known manifests are incompatible between v1.5 and v1.6. But I don’t understand your struggle with binder: in binder i usually use the same version of Julia I test my code locally with. In Project.toml you can force a specific version of Julia to use in binder
2 Likes
Yes, struggle is the right word. No matter what I do I get Julia 1.5 in mybinder, which promptly chokes on the configuration files. Is there some magic that you use?
Up to 1.6 I’ve never even noticed that the config files might have been mismatched with the versions of the Julia exe. It just always worked.
Is it the entry
[compat]
julia = "1.6"
in Project.toml?
1 Like
Yes, that is what I’ve been playing with.
I don’t know exactly what binder does to install Julia, but there is no stable release of v1.6, that may be a problem 
That may be an aspect to consider, but one wouldn’t know it from the documentation: Choose languages for your environment — Binder 0.1b documentation.
Pinging @davidanthoff for how Binder installs Julia and whether Julia v1.6 can be used at the moment