Forced to use juliaup: not cool

Tooling VS Code
1

The new version of vscode Julia extension does not pick up the julia.exe in the path, but rather insists on using juliaup to install (some version of) it. Not very nice. I mean, I have the whole thing set up with a place for the depot etc. and that goes out the window. I am not sure where to inquire as to how to go back to something less intrusive. So, if you are listening, please do tell. Thanks.

11 Likes
2

It also sounds like a bug, so maybe open an issue at: GitHub - julia-vscode/julia-vscode: Julia extension for Visual Studio Code

2 Likes
3

They changed the logic.
It i s not enough anymore to have just julia.exe in path.
It means the latest updates just break fully working configuration which just had julia.exe in path.

I find this to be a wrong choice.
Choosing to promote a tool which makes sense to developers over a regular use.

5 Likes
4

Although I understand your frustration, I donā€™t understand why some people are against juliaup. I have read some thread about this and the supposed difficulty of installing julia on Windows.

To me, downloading the Julia installer, creating an environment variable to access julia everywhere or downloading juliaup installer and typing in a terminal juliaup add is equally ā€œdifficultā€.

I may miss something and I really want to understand why recommending people installing julia from juliaup is a bad thing or a bad choice.

In Python, managing installation is a nightmare if you donā€™t want to pollute your OS. You have to create an environnement, etc. That is why, I now use uv, which is basically juliaup + Pkg.

1 Like
5

This should only be happening if the julia.executablePath setting is completely empty.
In that case we nudge you towards either using juliaup or explicitly referencing a binary there (including a simple julia or julia.exe).

If this is happening when the setting is not empty, then please open an issue and include details for your setup.

1 Like
6

Actually Iā€™d argue it is the easiest on Window.

  1. Unzip the Zip file to whenever you want (Say MyJulia).
  2. Add the path of MyJulia\bin to path either permanently or per terminal session.
  3. Launch any application which is julia.exe dependent.

This easiness created many cases where people built a Portable Julia.

The last update of the extension changed that specific logic.
In past time, it would conclude if julia.exe is on path and use that.
The update require you to specify it explicitly.
Until you specify it, it keeps recommending juliaup.
This cause currently working configurations to stop working by updating the VS Code extension.
Not only that the user previous configuration stops working, suddenly you get messages about changing the way the user works.

Iā€™d be happy to hear the logic in this change. If it was the policy to begin with, I might see it. But breaking working configuration. Iā€™d assume there is a good motivation for that.

7

Pleeeease revert that.

1 Like
8

Other than the reasons mentioned by Roy, Iā€™ll add,

I want to stay with Julia 1.10 and I donā€™t want to fight with the system to be able to do that.

1 Like
9

You mean this fight?

juliaup add 1.10
juliaup default 1.10
2 Likes
10

It is cool, that itā€™s so easy with juliaup.
It is also cool, if someone wantā€™s to do it their way.

BOTH IS EQUALLY COOL.

No discussion needed.

Please donā€™t force anybody to anything. I see itā€™s probably only a bug!

11

Putting julia/julia.exe into the julia.executablePath setting should fully recover the previous behaviour. If it doesnā€™t, open an issue.

I get that changes in default behaviour are annoying, but this is fixable with a click and five keystrokes starting from the modal popup.

That said,

may fix the issue, but needs a some more testing before Iā€™m comfortable merging it.

2 Likes