4 ms·
Every release I am downloading Julia and trying to wrestle through some tutorials. Every time (0.4.0, 0.6.0, 1.0.0) I get stuck at some error, usually during th
by LittlePeter 8y ago
Every release I am downloading Julia and trying to wrestle through some tutorials. Every time (0.4.0, 0.6.0, 1.0.0) I get stuck at some error, usually during the pre-compiling of some dependency.
For example, I have downloaded julia-1.0.0. I try to follow this tutorial here, linked in this post by someone: http://juliadb.org/latest/manual/tutorial.html http://juliadb.org/latest/manual/tutorial.html
Then I do this and get an error:
julia> using JuliaDB
[ Info: Precompiling JuliaDB [a93385a2-3734-596a-9a66-3cfbb77141e6]
ERROR: LoadError: UndefVarError: start not defined
Stacktrace:
Every time. Even the screenshot of Julia code that julialang.org used to have was not runnable per admission of core devs.
What am I doing wrong? How are you able to run large Julia programs successfully?
Edit:
Let's try tutorial at https://www.analyticsvidhya.com/blog/2017/10/comprehensive-tutorial-learn-data-science-julia-from-scratch/ https://www.analyticsvidhya.com/blog/2017/10/comprehensive-t.... First command: Pkg.add("IJulia"): command fails to install dependency Conda.
Same for the tutorial at http://ucidatascienceinitiative.github.io/IntroToJulia/Html/ToolingDocumentationCommunity http://ucidatascienceinitiative.github.io/IntroToJulia/Html/...
Sigh. Give up
- KenoFischer 8y agoAfter every release the package ecosystem usually takes a few weeks to catch up. I'd recommend trying 0.6 until then.
- ontouchstart 8y agoIs it possible for the Julia team to make a short tutorial that does not depend on any external packages? Just show the new features in a fresh installation on a clean machine downloaded from https://julialang.org/downloads/ https://julialang.org/downloads/ . That would help a lot of people get started.
- chappi42 8y ago> Every time (0.4.0, 0.6.0, 1.0.0) I get stuck You should have tried 0.4.2, 0.6.3, 1.0.1. Motto: Don't start too fast and be slow giving up ;-)
- LittlePeter 8y agoThanks for the tip :-)
- ScottPJones 8y agoYes, if you want stability, you should never use a x.0 or x.0.0 release (even from a big company - how many people remember Windows 3.0? ) I, however, am a bit crazy, and enjoy living on the bleeding edge, and so am up late tonight hacking making sure all my packages are working correctly on v1.0.0 of Julia!
- ChrisRackauckas 8y agoIt was literally released today. Of course the packages don't work yet...
- LittlePeter 8y agoThat makes sense. Maybe I was used to R (CRAN) where uploaded packages are actually tested against the version they declare to support.
- candhee 8y agoJuliaDB declares support for 0.6 not 1.0 - http://juliadb.org/latest/ http://juliadb.org/latest/ Which package declared support for 1.0.0 and didn’t compile?
- kgwgk 8y agoA binary package will be available in CRAN for a given platform/version only if it works (it passes all the tests). It seems that Julia lets you install a non-working package without any warning (you will probably get errors when you run it, but I guess it may also fail silently which is worse).
- et2o 8y agoI was excited to try using Julia 1.0.0 today after a couple years since my last try and... couldn’t. None of the packages work with it yet. I guess I could go find an older version, but it seems like a problem that Julia will happily allow you to install a package it isn’t compatible with. What’s the point of the Pkg system then? CRAN’s model makes a lot more sense.
- StefanKarpinski 8y agoMany packages have declared them selves compatible with any future version of Julia... which is clearly a lie. These need upper bounds on their version compatibility, but that will take some time to propagate through the system.