-
-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auto Pkg manager fails when using JULIA_DEPOT_PATH different from default ".julia" #2586
Comments
Sorry in advance for nagging. Been a little while since I posted this. Any progress? This issue means I need to hack my Julia workshop prep. Giving my course one year later and this issue is still open. My use case is this: When running a workshop, I want to use a fresh DEPOT to more realistically simulate what Julia beginners will encounter during the workshop (and make testing of my workshop more reliable). I realise we are all very busy, but it would be good to have some idea of where this might go, if anywhere. |
Hey @ablaom, thanks for the reminder! I'll take a look |
Weird, it looks like running Running Running
Which says that it's installing registries... which means that it's a different folder. |
I made f135748 to prevent this in the future. Thanks for the nice issue report with a video! |
Ahh. That's a little embarrassing. Thanks for sorting this out for me. |
In a completely new Julia Depot I add Pluto.jl to the default env, do
using Pluto; Pluto.run()
and in a new notebook tryusing Example
. This leads to error message below. Julia version = 1.9.0 but Julia 1.8.5 has the same issue. I've tried some earlier patch releases of Pluto within 0.19.* but get same issue.pluto_fail.mov
The pluto script, after fail
The text was updated successfully, but these errors were encountered: