Never mind. This was a 64 bit to 32 bit conflict. Message didn't help,
but a bunch of searches did. Comment on doc stands, but user error was the
culprit.
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.
>
>
