Open axsk opened 4 years ago
Yes, this is a good point.
I think in general we might want to tweak what we have right now in the following way:
JULIA_LOAD_PATH
to make sure this new env always gets loaded as a stacked environmnt. The main benefit of this change would be that a) we don't modify the users project, and b) the IJulia.jl stuff is also available for other projects.Manifest.toml
s (with accompaning Project.toml
s) and instantiate and precompile all of the environments we find during the build phase, not just the one in the root as we do right now.@NHDaly, does that make sense to you?
Hey all, I'd like to start with saying that all this here is really great!
I stumbled across the following problem though: When having a Julia package with the following structure
and I open the
mynotebook.ipynb
in Jupyter, it usually (local Jupyter installation) uses thenotebooks
-localProject.toml
file. (Defaulting to@.
, c.f. https://github.com/JuliaLang/IJulia.jl/pull/820)/ When using repo2docker though, the behaviour is different. It now reads the Packages'Project.toml
.I think this is due to: https://github.com/jupyter/repo2docker/blob/bbc3ee02c0755b15ea456f9ae18dd76b904568e7/repo2docker/buildpacks/julia/julia_project.py#L139
With the default IJulia behaviour it is possible to publish a Julia package, which contains only the necessary dependencies whilst still having an example environment (notebooks) with additional dependencies (e.g. PyPlot.jl). (This still leaves the problem that the
requirements.txt
for thematplotlib
dependency is still in projects' main directory though)A hotfix would be prepending
]activate .
but would that be the intended way?Pinging @davidanthoff