Gaurav Wasnik (Jan 25 2021 at 16:12): Gaurav Wasnik (Jan 25 2021 at 16:12):I'm trying to install DFTK.jl package in JuliaPro.
The error I'm getting is
(v1.0) pkg> add DFTK
ERROR: The following package names could not be resolved:
* DFTK (not found in project, manifest or registry)
Please specify by known `name=uuid`.
However, earlier while using the REPL only, that is, the basic(?) Julia version, I faced no difficulty installing DFTK.jl and it worked fine.
Sorry if this is a very newbie question :sweat_smile:
Kevin Bonham (Jan 25 2021 at 16:25):When you say "Basic" julia version, do you mean Julia version 1.0 as opposed to another version? Looking at that package's Project.toml, I notice that it lists compatibility only with julia version 1.4 and above, and it looks like you're on julia version 1.0. It's possible there are no versions of the package that are known to work with julia v1.0
Is there some reason to be on julia v1.0? If you're able, I'd suggest using the most recent stable version (currently v1.5)
Gaurav Wasnik (Jan 25 2021 at 16:32):Oh got it! It was because I had reinstalled Julia a short while ago, and by mistake installed the LTS v1.0.5-2 version.
Thanks!
Kevin Bonham (Jan 25 2021 at 16:59)::thumbs_up:
Kevin Bonham (Jan 25 2021 at 17:00):Hope you don't mind, I updated the subject of the thread to more accurately reflect the content. Just in case someone comes searching later, it might make it easier to find
Gaurav Wasnik (Jan 25 2021 at 17:18):I'm still getting the same error
(@JuliaPro_v1.5.3-1) pkg> add DFTK
ERROR: The following package names could not be resolved:
* DFTK (not found in project, manifest or registry)
What is going wrong here?
Kevin Bonham (Jan 25 2021 at 17:46):Now it looks like you're on julia pro. Was that intentional? I don't have much experience with that, but it seems like it should work
Gaurav Wasnik (Jan 25 2021 at 17:49):Yes, I'm on pro. (And by 'basic' earlier I meant the standard Julia installation, DFTK.jl was working fine there).
What else could I try to resolve the issue?
Expanding Man (Jan 25 2021 at 17:53):Does pro link to a different registry by default? that would seem silly, but I guess it's possible
Frederik Banning (Jan 25 2021 at 17:53):My simple advice would be to ditch the so-called JuliaPro installation (which is limiting by definition) and just use a standard Julia installation which works perfectly fine and has nothing to do with being basic.
Expanding Man (Jan 25 2021 at 17:54):no offense to the julia computing guys, but frankly I can't imagine what juliapro is doing for anybody right now
Frederik Banning (Jan 25 2021 at 17:55):
Expanding Man (Jan 25 2021 at 18:00):I wonder if perhaps Julia is now successful enough that all the previous incentives for them to offer something like JuliaPro have vanished. I can see that due to the perversity of the software world, there was initially some incentive for them to do something like that, because getting large bureaucratic institutions to adopt new programming languages is a near impossible task, and many of them would place a completely inappropriate value on bullshitting together some bunch of random stuff into something that looks to them like what they call a "product" (whatever the hell that means), but Julia is a lot more mature, and much more widely used now. It seems a lot less likely that even some unwieldy institution would insist on some dubiously supported kitchen sink package over the tried-and-true default binary builds.
Gaurav Wasnik (Jan 25 2021 at 18:08):I'm new to Julia and I thought that long time Julia users all use JuliaPro. My personal motivation for switching to pro was to try out the Juno IDE which comes by default with pro.
Now this makes me wonder what environment do you all use? I could use a recommendation!
Max Köhler (Jan 25 2021 at 18:09):If you want an IDE Experience like JetBrains, RStudio, Eclipse whatever, then use VSCode + Julia plugin
Expanding Man (Jan 25 2021 at 18:10):you can use Juno, VS code or anything else with the regular Julia binaries, you don't need to use pro. The community uses a wide variety of editors, especially neovim, emacs, Juno (atom) and VS code (I know Juno is supposed to be on VS code at some point, but I don't know if they've done that yet). Some people also use jupyter or pluto notebooks.
Expanding Man (Jan 25 2021 at 18:10):but none of this in any way requires Julia pro
David Weingut (Jan 25 2021 at 18:11):I used JuliaPro until quite recently, mainly for Juno and being used to standard, easy installation over self installing binaries, but switched to "vanilla" Julia for better upgradability. I never had any problems with JuliaPro and don't think this error occurred because of a registry difference but can't say for sure.
David Weingut (Jan 25 2021 at 19:04):I withdraw my previous statement. The registry is indeed different, namely https://pkg.juliacomputing.com/registry/JuliaPro. One could test this by running registry status in the pkg prompt. You could add the general registry by running registry add https://github.com/JuliaRegistries/General.git afaik.
Apparently my package needs always consisted of only the common packages.
Argel Ramírez Reyes (Jan 26 2021 at 20:28):Expanding Man said:
no offense to the julia computing guys, but frankly I can't imagine what juliapro is doing for anybody right now
I've some times found that after long convincing efforts, pythonist friends finally try julia. They find juliaPro, try it and then decide that I was crazy all along because it gives more problems than solutions.
Mason Protter (Jan 26 2021 at 20:30):Yeah, I think JuliaPro is a good product, but it's confusingly marketed. First, it seems like a paid service but it's not, and second it's kinda the opposite of a professional product. It's more like 'julia curated' than 'professional'
Eric Forgy (Jan 26 2021 at 20:37):My only experience with JuliaPro is when people come to Slack/Zulip with problems. My advice is usually, "Don't use JuliaPro." More often than not, the problem goes away.
Christopher Rackauckas (Jan 26 2021 at 21:06):The problem really comes down to fixed versions of some packages like Reexport, StaticArrays, DataFrames, etc. can be blocking. JuliaPro is a good release process for Pumas though. The VS Code JuliaPro will have even less Pkg tricks, so more and more it'll work just like the standard release. v1.6 with JuliaPro VS Code and the Julia Hub plugin is pretty awesome.
Last updated: Nov 22 2024 at 04:41 UTC