With path to the exe, this is what I get:
LoadError: Couldn't find libpython; check your PYTHON environment variable
while loading C:\Users\Lewis\.julia\v0.4\PyCall\deps\build.jl, in
expression starting on line 17
So, the path needs to be to something else.
Of course, the real solution is the include the right path in the system
PATH variable. I have paths to the exe, to scripts, and to site packages,
which is the standard thing to do. But, Julia doesn't agree with this.
Lots of wasted frustration on something that should be simple but for
clearer documentation.
On Thursday, October 15, 2015 at 3:02:54 PM UTC-7, le...@neilson-levin.org
wrote:
>
> For building PyCall and other integrations to Python, need to set:
>
> let user_data_dir
> ENV["PATH"] =
> JULIA_HOME*";"*joinpath(JULIA_HOME,"..","Git","bin")*";"*ENV["PATH"]
> #haskey(ENV,"JULIA_EDITOR") || (ENV["JULIA_EDITOR"] = "start") #start
> is not a program, so this doesn't work
> ENV["PYTHON"] = "C:\\Program Files
> (x86)\\WinPython-32bit-2.7.9.5\\python-2.7.9\\python.exe"
> end
>
> EXACTLY what must the path in ENV["PYTHON"] point to? Please don't
> recommend conda, ok? I have 2 installs to Python already with lots of
> packages, including Matplotlib and Numpy. Don't want to manage yet another.
>
> Should the path point to the python executable? It's dll? Or to the
> directory that contains the python executable. PyCall documentation is
> rather vague on the point: If you want to use a different version of
> Python on your system, you can change the Python version by setting the
> PYTHON environment variable and then re-running Pkg.build("PyCall"). In
> Julia:
>
> ENV["PYTHON"] = "... path of the python program you want ..."
> Pkg.build("PyCall")
>
> That's a little bit too loose. Path directly to the exe or to the folder
> containing the exe. I've tried both and neither
> see to work.
>
>
