I got other errors upon re-install and from there Daniel Hoegh has provided
me with the answer I was looking for at:
https://groups.google.com/forum/#!searchin/julia-users/PyPlot$20not$20working$200.4.0/julia-users/kZQrK8-nmQ8/r6rPDeQtocYJ
Can you provide more details about how to do this?
On Wednesday, November 4, 2015 at 9:30:42 PM UTC-5, le...@neilson-levin.org
wrote:
>
> I did not build Julia from source. But, I am back in business using
> system Python. Never got conda to build everything on Windows.
>
>
Can you give more info about how to do this?
I did not build Julia from source. But, I am back in business using system
Python. Never got conda to build everything on Windows.
On Wednesday, November 4, 2015 at 2:19:18 PM UTC-8, Luke Stagner wrote:
>
> It will only work if you installed from source(I.e cloned the main Julia
> repository a
Not working Computer #2, continued from above, (was cut off):
>_
>
> julia> Pkg.status()
> 4 required packages:
> - MAT 0.2.14
> - Plots 0.4.2
> - PyCall1.1.2
> - PyPlot2.1.1
>
On windows machine #1 I've un/re-installed again for a *third *time and it
actually fixed it!
On windows machine #2 I've un/re-installed many times over and it's still
not working.
However the two machines seem identical to me, not sure what the difference
is.
Working Computer #1 says:
I tried uninstalling and re-installing before posting here on the google
group. I tried un/re-install again now and I am still back where I started.
Doing Pkg.add("PyCall") the info messages displayed say "No system-wide
Python was found; ... etc. ... using the Python distribution in the Conda
It will only work if you installed from source(I.e cloned the main Julia
repository and manually compiled). If you did that the directory would
usually be in your home directory.
On Nov 4, 2015 2:10 PM, wrote:
> I have setup PyCall using a system Python (2.7.10). I get ERROR:
> ArgumentError: ha
I have setup PyCall using a system Python (2.7.10). I get ERROR:
ArgumentError: haskey of NULL PyObject
in plot at C:\Users\Lewis\.julia\v0.4\PyPlot\src\PyPlot.jl:457
Matplotlib works fine in IPython.
I'm stuck. Which directory needs git clean?
On Wednesday, November 4, 2015 at 2:03:32 PM UT
I noticed it happened after I updated anaconda. Perhaps something went
wrong there
On 11/04/2015 02:01 PM, le...@neilson-levin.org wrote:
I have the same problem. I am going back to using a system Python and
giving up on conda. Works fine on Mac (par for the course that things
tend to work
I have the same problem. I am going back to using a system Python and
giving up on conda. Works fine on Mac (par for the course that things tend
to work on Mac). I previously had Julia using matplotlib using WinPython.
Wanted to try the conda approach. Too many problems, though. Hours late
What directory is the julia repository in?
On Wednesday, November 4, 2015 at 1:37:19 PM UTC-8, Luke Stagner wrote:
>
> I recently had a similar error. To fix it I had to do
> git clean -xdf
>
> in the julia repository if you installed from source
>
> I found the fix in this PyCall issue
> https:
I recently had a similar error. To fix it I had to do
git clean -xdf
in the julia repository if you installed from source
I found the fix in this PyCall issue
https://github.com/stevengj/PyCall.jl/issues/65
On Wednesday, November 4, 2015 at 11:58:53 AM UTC-8, Tom Breloff wrote:
>
> You probab
You probably have a corrupted cache from whatever you were manually
changing. I recommend just deleting your "~/.julia/v0.4" and starting
again. I just did this on my windows machine (just to make sure it's not a
Plots issue) and after doing only "Pkg.add("Plots"); using Plots" it
completes witho
I did Pkg.checkout("PyCall"); Pkg.build("PyCall") and PyCall is now version
1.1.2 master. The using Plots command still gives the error:
ERROR: ArgumentError: Docile not found in path
in require at loading.jl:233
in stale_cachefile at loading.jl:439
in recompile_stale at loading.jl:45
On Monday, November 2, 2015 at 5:24:32 PM UTC-5, jda wrote:
>
> and everything worked fine on my windows machine (Julia 0.4.0 repl). Then
> it broke (possibly due to Pkg.update()? I don't remember at this point.).
> So I looked up a few things and now it seems that I must do
>
> ENV["PYTHON"]
Nope, still the same haskey of NULL error.
17 matches
Mail list logo