# Updating to 1.11.7 causes PyCall to fail to build

**URL:** <https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427>\
**Category:** General Usage\
**Tags:** question\
**Created:** [September 16, 2025, 7:01am UTC](https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427 "2025-09-16T07:01:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xing\_Shi\_Cai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xing_shi_cai/32/14128_2.png) [@Xing\_Shi\_Cai](https://discourse.julialang.org/u/Xing_Shi_Cai)\
**Post date:** [September 16, 2025, 7:01am UTC](https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427/1 "2025-09-16T07:01:11Z")

</div>

I just updated Julia from 1.11.6 to 1.11.7. Then some of my packages such as PyCall cannot be built any more. Here’s the error —

```julia-auto
    Building Conda ─→ `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/b19db3927f0db4151cb86d073689f2428e524576/build.log`
    Building PyCall → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/9816a3826b0ebf49ab4926e2b18842ad8b5c8f04/build.log`
ERROR: Error building `PyCall`: 

# All requested packages already installed.

┌ Info: Using the Python distribution in the Conda package by default.
└ To use a different Python version, set ENV["PYTHON"]="pythoncommand" and re-run Pkg.build("PyCall").
[ Info: Running `conda install -y --satisfied-skip-solve numpy` in root environment
ERROR: LoadError: Couldn't find libpython; check your PYTHON environment variable.

The python executable we tried was /home/xing/.julia/conda/3/bin/python (= version 3.12).
Re-building with
    ENV["PYCALL_DEBUG_BUILD"] = "yes"
may provide extra information for why it failed.

Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:35
 [2] find_libpython(python::String; _dlopen::typeof(Base.Libc.Libdl.dlopen))
   @ Main ~/.julia/packages/PyCall/1gn3u/deps/buildutils.jl:80
 [3] find_libpython(python::String)
   @ Main ~/.julia/packages/PyCall/1gn3u/deps/buildutils.jl:48
 [4] top-level scope
   @ ~/.julia/packages/PyCall/1gn3u/deps/build.jl:82
 [5] include(fname::String)
   @ Main ./sysimg.jl:38
 [6] top-level scope
   @ none:5
in expression starting at /home/xing/.julia/packages/PyCall/1gn3u/deps/build.jl:43

```

Any suggestions?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [September 16, 2025, 11:20am UTC](https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427/2 "2025-09-16T11:20:56Z")

</div>

Are you using Juliaup? If so, can you show the output of `versioninfo()`? There was an issue in Juliaup, it’s possible you got a wrong build of Julia (32-bit instead of 64-bit, which _works_ for most stuff, but it’s not what you’d like to use).

---

<div class="post-metadata">

**Author:** ![Xing\_Shi\_Cai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xing_shi_cai/32/14128_2.png) [@Xing\_Shi\_Cai](https://discourse.julialang.org/u/Xing_Shi_Cai)\
**Post date:** [September 16, 2025, 2:55pm UTC](https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427/3 "2025-09-16T14:55:53Z")

</div>

Yes. I am using juliaup. It is a bit strange because I just tried updating on my second computer. It works fine. So maybe juliaup has been fixed. I will try tomorrow on the computer which has an issue.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [September 16, 2025, 3:02pm UTC](https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427/4 "2025-09-16T15:02:30Z")

</div>

> [@Xing\_Shi\_Cai](#):
>
> So maybe juliaup has been fixed.

Yes:

> [@Julia v1.11.7 has been released](https://discourse.julialang.org/t/julia-v1-11-7-has-been-released/132437/1):
>
> Apologies to anybody who ran into issues yesterday; the permissions on the binaries were initially set incorrectly, which cascaded through the multi-step release process in a way that wasn’t visible until the end, leaving things in a weird state. We’ll be working to make the overall process more robust to avoid disruptions in the future.

Simply updating Juliaup should now fix your issues.

---

<div class="post-metadata">

**Author:** ![Xing\_Shi\_Cai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xing_shi_cai/32/14128_2.png) [@Xing\_Shi\_Cai](https://discourse.julialang.org/u/Xing_Shi_Cai)\
**Post date:** [September 17, 2025, 7:07am UTC](https://discourse.julialang.org/t/updating-to-1-11-7-causes-pycall-to-fail-to-build/132427/5 "2025-09-17T07:07:47Z")

</div>

I tried to update juliaup but was told

```julia-auto
Checking for new Julia versions
Checking for self-updates
Juliaup unchanged on channel 'release' - 1.18.0

```

In any case, rerun `juliaup update` now successfully update to Julia 1.11.7.