On Thursday, October 8, 2015 at 10:42:38 AM UTC-4, Luthaf wrote:
>
> I guess that is a bug in PyCall, so you should do your bug report there :
> https://github.com/stevengj/PyCall.jl/issues/new. Please ping me
> (@Luthaf) on the issue, because this might be related with Conda.jl
>
Conda.PYTHONDIR was defined in recent versions of Conda, so I'm guessing
you have an out-of-date Conda. That, combined with the fact that your
PyCall package was not already built the first time you tried it, leads me
to suspect that you did a Pkg.checkout("PyCall") at some point to get the
latest (master) version. By doing this, you turned off automatic
dependency management, which is why you were able to update PyCall without
updating Conda.
I would do Pkg.free("PyCall") to go back to the official version, then do
Pkg.update() to get the latest versions of your packages. This should
update Conda too, and Pkg.build("PyCall") should then install Conda's
Python if you don't have one already.
