Here's the latest commit on my local Atom.jl:
colin@colin:~/.julia/v0.4/Atom$ git log
commit e2d2bd6d4be24acfe72f8e3d91291b424af70512
Merge: 2d78ca1 72a050a
Author: Mike J Innes <[email protected]>
Date: Sat Sep 19 10:13:45 2015 +0100
Merge pull request #9 from ssfrr/depwarn-0_4
fixes some deprecation warnings loudly complaining on recent 0.4.0
builds
That matches the latest commit on the master branch on github. Similarly,
for local CodeTools:
commit d9fca7ef3145e78d75e9d9050968440dae877906
Merge: 76e3c53 cd177a0
Author: Mike J Innes <[email protected]>
Date: Fri Oct 23 14:18:41 2015 +0100
Merge pull request #6 from ssfrr/depwarn_fieldnames
fixes deprecated names method usage
which also looks about right.
Just to provide one other potentially useful bit of information, I
Pkg.free'd Atom, CodeTools, and JuliaParser, Pkg.rm'd them, then added them
back in, and ran Pkg.checkout over all three of them. Then a Using Atom.
All done at the REPL. Here is the output:
julia> Pkg.checkout("Atom")
INFO: Checking out Atom master...
INFO: Pulling Atom latest master...
INFO: No packages to install, update or remove
julia> Pkg.checkout("CodeTools")
INFO: Checking out CodeTools master...
INFO: Pulling CodeTools latest master...
INFO: No packages to install, update or remove
julia> Pkg.checkout("JuliaParser")
INFO: Checking out JuliaParser master...
INFO: Pulling JuliaParser latest master...
INFO: No packages to install, update or remove
julia> using Atom
INFO: Recompiling stale cache file /home/colin/.julia/lib/v0.4/Atom.ji for
module Atom.
INFO: Recompiling stale cache file /home/colin/.julia/lib/v0.4/CodeTools.ji
for module CodeTools.
INFO: Recompiling stale cache file /home/colin/.julia/lib/v0.4/JuliaParser.ji
for module JuliaParser.
Does that look right?
Also, after doing this, "git pull origin master" on all three packages
states that they're already up-to-date.
Cheers and many thanks,
Colin
On Wednesday, 28 October 2015 18:41:58 UTC+11, Spencer Russell wrote:
>
> Try running "git pull" from within the package directories. Maybe you're
> on local master but don't have all the commits from remote? What's the most
> recent commit you see in Atom.jl and CodeTools.jl?
>
> -s
>
> On Oct 27, 2015, at 10:03 PM, [email protected] <javascript:> wrote:
>
> Done. Precompilation occurred at the REPL, and I didn't have to do it
> within Atom. Verified packages are all on Master. Unfortunately, I'm still
> getting all of the original deprecation warnings when evaluating from the
> editor in Atom.
>
> I'm happy to pursue this further, but am equally happy to wait it out if
> you're running short on ideas or time.
>
> Cheers and thanks,
>
> Colin
>
> On Wednesday, 28 October 2015 12:24:38 UTC+11, Spencer Russell wrote:
>>
>> You’re running into another known issue:
>> https://github.com/JuliaLang/julia/issues/12941
>>
>> Try opening a normal REPL in the terminal and run “using Atom” to trigger
>> the precompilation, then it shouldn’t need to happen when you run from Atom.
>>
>> -s
>>
>>
>> On Oct 27, 2015, at 9:09 PM, [email protected] wrote:
>>
>> Ah... understood. Many thanks.
>>
>> I'm afraid I'm still not getting the desired result however. After
>> running checkout on "Atom", "CodeTools" and "JuliaParser" I run
>> Pkg.status() and can verify I'm on the master branch for all 3. So I fire
>> up Atom again, try to evaluate in the editor, and get the following error:
>>
>> INFO: Recompiling stale cache file
>> /home/colin/.julia/lib/v0.4/JuliaParser.ji
>> Julia has stopped: 1, null
>>
>> So I close down Atom, open it again, and try to evaluate in the editor
>> again. This time I get:
>>
>> INFO: Recompiling stale cache file
>> /home/colin/.julia/lib/v0.4/CodeTools.ji
>> Julia has stopped: 1, null
>>
>> Close down Atom one more time, re-open it and try again. Now I get:
>>
>> INFO: Recompiling stale cache file /home/colin/.julia/lib/v0.4/Atom.ji
>>
>> but everything is now working fine. Problem solved? Unfortunately not. I
>> restart Atom again and I'm back to all the deprecation warnings, even
>> though Pkg.status() indicates I'm still on the master branch for Atom,
>> CodeTools, and JuliaParser.
>>
>> Apologies for the long message. Also, if this is one of those things that
>> will resolve itself over the next couple of weeks as changes from master
>> are pushed to the more stable branches, then I'm happy to ignore the
>> warnings for the time being and not waste anyone's time any further with
>> what is essentially a minor inconvenience.
>>
>> Cheers,
>>
>> Colin
>>
>>
>>
>>
>> On Wednesday, 28 October 2015 11:37:21 UTC+11, Spencer Russell wrote:
>>>
>>> `Pkg.checkout(…)` operates an an already-installed package, so it must
>>> be run after `Pkg.add(…)`.
>>>
>>> -s
>>>
>>> On Oct 27, 2015, at 8:31 PM, [email protected] wrote:
>>>
>>> I suppose I could clone the master branch. Is that a bad idea?
>>>
>>> On Wednesday, 28 October 2015 11:30:43 UTC+11, [email protected]
>>> wrote:
>>>>
>>>> Thanks for responding.
>>>>
>>>> Pkg.checkout("Atom") gives me the error:
>>>>
>>>> ERROR: Atom is not a git repo
>>>> in checkout at pkg/entry.jl:203
>>>> in anonymous at pkg/dir.jl:31
>>>> in cd at file.jl:22
>>>> in cd at pkg/dir.jl:31
>>>> in checkout at pkg.jl:37
>>>>
>>>> (I originally did try using Pkg.checkout as per the instructions, but
>>>> got this error, and so went with Pkg.add instead).
>>>>
>>>> Any thoughts or is this a bug?
>>>>
>>>> Cheers,
>>>>
>>>> Colin
>>>>
>>>>
>>>> On Wednesday, 28 October 2015 11:23:30 UTC+11, Jonathan Malmaud wrote:
>>>>>
>>>>> You want to be on the master versions:
>>>>>
>>>>> Pkg.checkout("Atom")
>>>>> Pkg.checkout("CodeTools")
>>>>>
>>>>
>>>
>>
