# Plot problem

**URL:** <https://discourse.julialang.org/t/plot-problem/6067>\
**Category:** New to Julia\
**Created:** [September 25, 2017, 5:22pm UTC](https://discourse.julialang.org/t/plot-problem/6067 "2017-09-25T17:22:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)\
**Post date:** [September 25, 2017, 7:20pm UTC](https://discourse.julialang.org/t/plot-problem/6067/4 "2017-09-25T19:20:04Z")

</div>

I’m afraid I don’t know much about debugging python-julia issues on Windows, and I can’t test this myself. However, one thing you might try is forcing PyCall (and, thus, PyPlot) to use its own self-contained Python version instead of whatever you may have on your system. Can you try running:

```julia
using PyCall
PyCall.python

```

if that outputs a version inside `.julia/v0.6/Conda/deps/usr/bin/python` then you’re already using a self-contained Python version and this won’t help. But if it shows some other path on your computer, then you can try:

```julia
ENV["PYTHON"] = ""
Pkg.build("PyCall")
Pkg.build("PyPlot")

```

Failing that, if all you want to do is plot things using Plots.jl, you can just switch to a different backend. I like `GR.jl`:

```julia
Pkg.add("GR")
using Plots
gr()
plot([1,2,3])

```

---

_[View the full topic](https://discourse.julialang.org/t/plot-problem/6067)._
