Yes, this is exactly what I did and the whole thing ran and now I am
chugging along.
The very last step just before that was resetting the PYTHONHOME to
C:\Anaconda from earlier setting of C:\Anaconda;C:\Anaconda\Scripts. And it
did not work.
Then you suggested the change to PYTHONHOME should have only one file
reference. I changed and PyPlot still did not run.
The next step was as again what you suggested
pyinitialize("C:\\Anaconda\\python") and this ran.
Now unless this set up everything - that is a different story.
I closed Julia window, opened the pycall.jl file and made the change that I
wrote above about which you expressed surprise.
And then restarted Julia and without using PyCall went ahead with using
PyPlot. Everything went fine.
If you want I can undo my change to pycall.jl and let you know?On Mon, Jan 27, 2014 at 5:14 PM, Steven G. Johnson <[email protected]>wrote: > > > On Monday, January 27, 2014 3:57:50 PM UTC-5, Rajn wrote: >> >> Ok, I got it now to run it without using PyCall and pyinitialize. >> >> I just changed PyCall line where ENV variable is set i.e., >> >> changed from [ENV] = @windows exec_prefix: preconfigvar(...,"prefix") etc >> to >> [ENV] = exec_prefix >> >> > Wait, what? You changed > > ENV["PYTHONHOME"] = @windows? exec_prefix : pyconfigvar(python, > "prefix") * ":" * exec_prefix > > to > > ENV["PYTHONHOME"] = exec_prefix > > ?? But on Windows (where @windows is true), those two lines should be > exactly equivalent! Did I misunderstand you? > > --SGJ > > PS. I just tried a fresh Windows 8.1 x64 machine. Installed Anaconda > (64-bit), installed Julia 0.2 (64-bit), ran Pkg.add("PyPlot"); > Pkg.add("IJulia") in julia, and then ran "ipython notebook --profile julia" > at the Windows command prompt. Everything seems to work fine, no patches > required. >
