The problem magically fixed itself today. I was running a Pkg.checkout() on "Distributions" to move to the master branch there to get rid of deprecation warnings generated by qq.jl. In the process, I ran a Pkg.update(), and re-compiled other pre-compiled packages. Problem gone.
At this stage I've only one possible explanation. I had not re-compiled Atom.jl and CodeTools.jl since moving the master branch for the Atom plugins "language-julia", "julia-client", and "ink". Perhaps the order there is important, i.e. one needs to move to master branch for Atom plugins, and THEN move to master branch for Atom.jl and CodeTools.jl and pre-compile. I could test this theory out I suppose, but then I face the very real possibility of re-introducing the problem and not being able to get rid of it... I hope this is of help to someone. Cheers, Colin On Wednesday, 28 October 2015 10:57:43 UTC+11, [email protected] wrote: > > Hi all, > > I'm using Julia v0.4 with the Atom package, on Atom 1.0 with the packages > ink, julia-client, and language-julia (and I'm really enjoying this as an > IDE solution). > > I can toggle the Julia console in Atom, and enter code directly into it > without any errors or warnings. However, as soon as I try to evaluate a > line of code from the Atom editor, I get a large number of deprecation > warnings, either of the form: > > WARNING: Base.Uint8 is deprecated, use UInt8 instead. > likely near no file:422 > > or > > WARNING: Base.Uint8 is deprecated, use UInt8 instead. > likely near no file:422 > in skip at /home/colin/.julia/v0.4/LNR/src/LNR.jl:171 > > Has anyone else encountered this and is there a fix? I had a look through > the LNR source, and there is nothing in it that should be triggering a > deprecation warning, nor is there even a line 171 (it only goes up to about > line 130). > > Note, I can just ignore the deprecation warnings, and continue on working > without a problem, so this isn't an urgent issue. Just wondering if I've > stuffed up the install process somehow. > > Cheers, > > Colin >
