PythonPlot v1.0.7 fails to precompile

[rozmanmg]

Upon attempting to using PythonPlot I am getting the following warning:

Info Given PythonPlot was explicitly requested, output will be shown live 
WARNING: Method definition axis(Any...) in module PythonPlot at /home/xxxxxx/.julia/packages/PythonPlot/Xa6bF/src/PythonPlot.jl:175 overwritten at /home/xxxxxx/.julia/packages/PythonPlot/Xa6bF/src/PythonPlot.jl:184.
ERROR: Method overwriting is not permitted during Module precompilation. Use `__precompile__(false)` to opt-out of precompilation.
  ? PythonPlot
WARNING: Method definition axis(Any...) in module PythonPlot at /home/xxxxxx/.julia/packages/PythonPlot/Xa6bF/src/PythonPlot.jl:175 overwritten at /home/xxxxxx/.julia/packages/PythonPlot/Xa6bF/src/PythonPlot.jl:184.
ERROR: Method overwriting is not permitted during Module precompilation. Use `__precompile__(false)` to opt-out of precompilation.
┌ Warning: Replacing docs for `PythonPlot.axis :: Tuple` in module `PythonPlot`
└ @ Base.Docs docs/Docs.jl:249

I have not had such a warning in the earlier versions of PythonPlot.

Way to reproduce: julia -e 'using Pkg; Pkg.activate(temp=true); Pkg.add("PythonPlot"); using PythonPlot'

Julia version:

$ julia -e "using InteractiveUtils; versioninfo()"
Julia Version 1.12.6
Commit 15346901f00 (2026-04-09 19:20 UTC)
Build Info:
  Official https://julialang.org release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 12 × 13th Gen Intel(R) Core(TM) i5-1335U
  WORD_SIZE: 64
  LLVM: libLLVM-18.1.7 (ORCJIT, alderlake)
  GC: Built with stock GC
Threads: 12 default, 1 interactive, 12 GC (on 12 virtual cores)
Environment:
  JULIA_DEPOT_PATH = /home/xxxxxx/.julia
  JULIA_NUM_THREADS = auto
  LD_ARGV0_REL = ../bin/vshd
  JULIA_EDITOR = emacsclient
  JULIA_PKG_DEVDIR = /home/xxxxxx/juliadev
  JULIA_CONDAPKG_BACKEND = Null
  JULIA_PYTHONCALL_EXE = /home/xxxxxx/.julia/conda/3/x86_64/bin/python
  JULIA_CONDAPKG_EXE = /home/xxxxxx/.julia/conda/3/x86_64/bin/conda

Possibly relevant part of startup.jl:

# https://juliapy.github.io/PythonCall.jl/stable/pythoncall/#pythoncall-config
# PythonCall settings for using the existing python and python packages
ENV["JULIA_CONDAPKG_BACKEND"] = "Null"
ENV["JULIA_PYTHONCALL_EXE"] = "/home/xxxxxx/.julia/conda/3/x86_64/bin/python"
ENV["JULIA_CONDAPKG_EXE"] = "/home/xxxxxx/.julia/conda/3/x86_64/bin/conda"

[deszoeke]

Me too. axis() is first defined on line 175, then clobbered on line 181.

Removing :axis from the list of function names on line 171 allows precompilation.
What needs to be tested?

[stevengj]

Whoops, should be fixed by #60.

I didn't notice it because for me it just gives a warning, not an error, on precompilation (Julia 1.12.6). Wonder why it is an error for you?

[stevengj]

1.0.8 should be out soon to fix this: JuliaRegistries/General#163097

[rozmanmg]

Thank you!

I didn't notice it because for me it just gives a warning, not an error, on precompilation (Julia 1.12.6). Wonder why it is an error for you?

Technically, it also was a warning for me. PythonPlot 1.0.7, after producing that long message, still was able to plot:

julia -e 'using Pkg; Pkg.activate(temp=true); Pkg.add("PythonPlot"); using PythonPlot; plot(rand(10))' -i -q 

Also, if I 'asked' just for the precompilation of an existing project with PythonPlot, the response was just a question mark symbol next to the package name:

$ julia -e 'using Pkg; Pkg.precompile()' 
  Activating project at `~/p2200/trinity-test`
  ? PythonPlot
$