Re: [julia-users] suggestion of OSX julia/ijulia setup
Many thanks Cameron, I'll try that setup. Did I understand that you use brew to compile julia? On Friday, May 16, 2014 4:21:19 PM UTC+2, Ethan Anderes wrote: +1 for Cameron. I use the same workflow.
Re: [julia-users] suggestion of OSX julia/ijulia setup
Hi Jon, No -- I pull julia via git on github, and compile by hand every few days. I've symlinked ~/bin/julia to the directory that I compile julia into, so julia is in my path. On 10.9, the native option is Clang, which works fine.. I've been able to dodge gcc (gnu) for all system dependencies so far. Homebrew seems to handle a lot of lib conflicts pretty well, unless you tap some obvious ones or do some forcing. Cameron On Sun, May 18, 2014 at 12:46 PM, Jon Norberg jon.norb...@ecology.su.sewrote: Also, I sometimes seem to get issues with what libraries are being used. I am not very good at this but I understand there are different compiler libraries and native osx ones. How do you guys handle this? or is it not an issue using brew? On Sunday, May 18, 2014 6:39:38 PM UTC+2, Jon Norberg wrote: Many thanks Cameron, I'll try that setup. Did I understand that you use brew to compile julia? On Friday, May 16, 2014 4:21:19 PM UTC+2, Ethan Anderes wrote: +1 for Cameron. I use the same workflow.
[julia-users] suggestion of OSX julia/ijulia setup
Hi all, I have been using julia and ijulia for a while and everything worked fine. over time I get more and more issues, trying to upgrade/reinstall etc and now I can't get it to work at all anymore. As I intend to reinstall osx anyway, I was wondering if you good people have any good setup for python/ijulia/julia/juliastudio that is simple to maintain over time. I want to use one version of julia so somehow let julia-studio use that (annoying that they hardcode the julia path to julia-basic...) I was ambitious to try to keep a --HEAD version of julia but maybe I will have to settle for a latest stable pre-release version to avoid trouble. But I also find that sometimes there are issues with the dependencies and libraries, how do you keep those right? So how do you people keep julia smoothly updating and working. Are you using brew, anaconda, enthought, for the python part, are you using xcode compiler or others, are you building julia yourself... I'd appreciate any help in setting this up for the longer run than I have been able to keep it working so far. Many thanks
Re: [julia-users] suggestion of OSX julia/ijulia setup
I am not sure if this appeals to you, but I'm happy to share my configuration. I just use the REPL and a decent editor (vim), which I'm happy with. I've been using this setup for the past couple months (mid-March). I've only had occasionally issues, but I follow HEAD so that is expected. I am now on 10.9, but this has been short enough that only a few deps have been updated via system homebrew. Things could break there, but never have. The situation I finally created was: - homebrew and then pip to install python / scipy / ipython (see iJulia docs) - git repo of Julia github/master - Pkg.add(...), Pkg.update(), etc. Ideally, I'm not sure I really need the julia homebrew which this uses by default. But it works, so I haven't worried about resolving this. 1. I pull and re-compile master every few days. I usually scan the dev / users list before that to look for any ongoing gotchas, or new github issues. 2. When I compile Julia, and I do a few tests (basic crunching, Winston plots via Cairo, iJulia) then I use a local tag in my git repo to signify the working version. It is just easier for me to roll things back, but certainly not strictly necessary. 3. I usually only Pkg.update() after I've confirmed a new Julia compiles and seems to work from the above tests. Most of the issues I've had were between 2 3 not being in sync. Some small changes where packages didn't catch up. I've been impressed with how quickly many of the authors have fixed things, so it's rarely been an issue. The one issue of Julia rollback I had to do was pretty easy (an issue that broke Grid.jl, I rolled back master for a couple days and watched the discussion / issue until it was resolved). I think this works as a lot of developers try and run real stuff with master, and most of the current packages are tracking master as the language develops. YMMV, but I've been satisfied with the stability of this. Cameron p.s. I tried using anaconda to pin the python previously, which worked, but had some issues. I was happier when I did homebrew only python.
Re: [julia-users] suggestion of OSX julia/ijulia setup
I follow an identical process to Cameron, with the same results. - Adrian. On Fri, May 16, 2014 at 3:37 PM, Cameron McBride cameron.mcbr...@gmail.comwrote: I am not sure if this appeals to you, but I'm happy to share my configuration. I just use the REPL and a decent editor (vim), which I'm happy with. I've been using this setup for the past couple months (mid-March). I've only had occasionally issues, but I follow HEAD so that is expected. I am now on 10.9, but this has been short enough that only a few deps have been updated via system homebrew. Things could break there, but never have. The situation I finally created was: - homebrew and then pip to install python / scipy / ipython (see iJulia docs) - git repo of Julia github/master - Pkg.add(...), Pkg.update(), etc. Ideally, I'm not sure I really need the julia homebrew which this uses by default. But it works, so I haven't worried about resolving this. 1. I pull and re-compile master every few days. I usually scan the dev / users list before that to look for any ongoing gotchas, or new github issues. 2. When I compile Julia, and I do a few tests (basic crunching, Winston plots via Cairo, iJulia) then I use a local tag in my git repo to signify the working version. It is just easier for me to roll things back, but certainly not strictly necessary. 3. I usually only Pkg.update() after I've confirmed a new Julia compiles and seems to work from the above tests. Most of the issues I've had were between 2 3 not being in sync. Some small changes where packages didn't catch up. I've been impressed with how quickly many of the authors have fixed things, so it's rarely been an issue. The one issue of Julia rollback I had to do was pretty easy (an issue that broke Grid.jl, I rolled back master for a couple days and watched the discussion / issue until it was resolved). I think this works as a lot of developers try and run real stuff with master, and most of the current packages are tracking master as the language develops. YMMV, but I've been satisfied with the stability of this. Cameron p.s. I tried using anaconda to pin the python previously, which worked, but had some issues. I was happier when I did homebrew only python.
Re: [julia-users] suggestion of OSX julia/ijulia setup
+1 for Cameron. I use the same workflow.
