# PythonPlot instead of PyPlot

**URL:** https://discourse.julialang.org/t/pythonplot-instead-of-pyplot/133923
**Category:** Visualization
**Tags:** pyplot, pythonplot
**Created:** [November 17, 2025, 6:01am UTC](https://discourse.julialang.org/t/pythonplot-instead-of-pyplot/133923 "2025-11-17T06:01:40Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![sparrowhawk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sparrowhawk/32/9148_2.png) [@sparrowhawk](https://discourse.julialang.org/u/sparrowhawk)
#### Post date: [November 17, 2025, 6:01am UTC](https://discourse.julialang.org/t/pythonplot-instead-of-pyplot/133923/1 "2025-11-17T06:01:40Z")

</div>

Hi all,

I’ve been having trouble with `matplotlib` dependencies within my package when using `PyPlot.jl` – most of these errors crop up when there are upstream changes within Conda/matplotlib, that show up during the compilation phase with Conda.jl and PyCall.jl when my package builds. Is there a lower likelihood of build errors if I switch to PythonPlot.jl which seems to use more modern interop machinery between julia and python?

Thanks!