# PyPlot conflict with Intel MKL?

**URL:** <https://discourse.julialang.org/t/pyplot-conflict-with-intel-mkl/720>\
**Category:** Numerics\
**Tags:** plotting\
**Created:** [December 4, 2016, 10:36am UTC](https://discourse.julialang.org/t/pyplot-conflict-with-intel-mkl/720 "2016-12-04T10:36:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stustd](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stustd/32/21430_2.png) [@stustd](https://discourse.julialang.org/u/stustd)\
**Post date:** [December 4, 2016, 10:36am UTC](https://discourse.julialang.org/t/pyplot-conflict-with-intel-mkl/720/1 "2016-12-04T10:36:22Z")

</div>

I’ve been invariably unsuccessful in trying to make PyPlot work with any Python 3.5 version that compiles Numpy against the (multicore) Intel MKL library (I have tried it with two versions: Intelpython35 from Intel Corp, and stock Python 3.5.2 with conda pkg manager installed – this automatically installs a MKL compatible numpy version). In the end success was only met with stock Python and Numpy compiled against openblas. Is my experience commonplace?

---

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [December 4, 2016, 11:42am UTC](https://discourse.julialang.org/t/pyplot-conflict-with-intel-mkl/720/2 "2016-12-04T11:42:08Z")

</div>

Yes, if you are using a Julia version compiled against MKL too…it’s often a problem if you are trying to link two pieces of software that link against slight different versions of a library. See [Pyplot segfaults and tries to access MKL libraries · Issue #165 · JuliaPy/PyPlot.jl · GitHub](https://github.com/JuliaPy/PyPlot.jl/issues/165)