Merge branch 'main' into fix-types

Author: MilesCranmer

.github/workflows/benchmark_pr.yml

@@ -0,0 +1,16 @@
+name: Benchmark PR
+on:
+  pull_request:
+
+jobs:
+  bench:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: MilesCranmer/AirspeedVelocity.jl@action-v1
+        with:
+          julia-version: "1"
+          tune: "true"
+          # Post to "summary" tab of workflow run:
+          job-summary: "true"
+          # Run benchmark using PR's version of the script:
+          bench-on: ${{ github.event.pull_request.head.sha }}

.github/workflows/tests.yml

@@ -93,6 +93,7 @@ jobs:
           uv run pytest -s --nbval --cov=pysrc ./pytest/
         env:
           PYTHON_JULIACALL_THREADS: '2'
+          PYTHON_JULIACALL_HANDLE_SIGNALS: 'yes'
 
       - name: Upload coverage to Codecov
         uses: codecov/codecov-action@v5

Project.toml

@@ -1,7 +1,7 @@
 name = "PythonCall"
 uuid = "6099a3de-0909-46bc-b1f4-468b9a2dfc0d"
 authors = ["Christopher Doris <github.com/cjdoris>"]
-version = "0.9.25"
+version = "0.9.26"
 
 [deps]
 CondaPkg = "992eb4ea-22a4-4c89-a5bb-47a3300528ab"

benchmark/Project.toml

@@ -0,0 +1,2 @@
+[deps]
+BenchmarkTools = "6e4b80f9-dd63-53aa-95a3-0cdb28fa8baf"

benchmark/benchmarks.jl

@@ -0,0 +1,62 @@
+using BenchmarkTools
+using PythonCall
+using PythonCall: pydel!, pyimport, pydict, pystr, pyrange
+
+const SUITE = BenchmarkGroup()
+
+function test_pydict_init()
+    random = pyimport("random").random
+    x = pydict()
+    for i in pyrange(1000)
+        x[pystr(i)] = i + random()
+    end
+    return x
+end
+
+SUITE["basic"]["julia"]["pydict"]["init"] = @benchmarkable test_pydict_init()
+
+function test_pydict_pydel()
+    random = pyimport("random").random
+    x = pydict()
+    for i in pyrange(1000)
+        k = pystr(i)
+        r = random()
+        v = i + r
+        x[k] = v
+        pydel!(k)
+        pydel!(r)
+        pydel!(v)
+        pydel!(i)
+    end
+    return x
+end
+
+SUITE["basic"]["julia"]["pydict"]["pydel"] = @benchmarkable test_pydict_pydel()
+
+@generated function test_atpy(::Val{use_pydel}) where {use_pydel}
+    quote
+        @py begin
+            import random: random
+            x = {}
+            for i in range(1000)
+                x[str(i)] = i + random()
+                $(use_pydel ? :(@jl PythonCall.pydel!(i)) : :(nothing))
+            end
+            x
+        end
+    end
+end
+
+SUITE["basic"]["@py"]["pydict"]["init"] = @benchmarkable test_atpy(Val(false))
+SUITE["basic"]["@py"]["pydict"]["pydel"] = @benchmarkable test_atpy(Val(true))
+
+
+include("gcbench.jl")
+using .GCBench: append_lots
+
+SUITE["gc"]["full"] = @benchmarkable(
+    GC.gc(true),
+    setup=(GC.gc(true); append_lots(size=159)),
+    seconds=30,
+    evals=1,
+)

benchmark/gcbench.jl

@@ -0,0 +1,13 @@
+module GCBench
+
+using PythonCall
+
+function append_lots(; iters=100 * 1024, size=1596)
+    v = pylist()
+    for i = 1:iters
+        v.append(pylist(rand(size)))
+    end
+    return v
+end
+
+end

docs/src/faq.md

@@ -10,14 +10,19 @@ To force PythonCall to use the same Python interpreter as PyCall, set the enviro
 
 Alternatively, to force PyCall to use the same interpreter as PythonCall, set the environment variable `PYTHON` to [`PythonCall.python_executable_path()`](@ref) and then `Pkg.build("PyCall")`. You will need to do this each time you change project, because PythonCall by default uses a different Python for each project.
 
-## Is PythonCall/JuliaCall thread safe?
+## [Is PythonCall/JuliaCall thread safe?](@id faq-multi-threading)
 
 Yes, as of v0.9.22, provided you handle the GIL correctly. See the guides for
 [PythonCall](@ref jl-multi-threading) and [JuliaCall](@ref py-multi-threading).
 
 Before, tricks such as disabling the garbage collector were required. See the
 [old docs](https://juliapy.github.io/PythonCall.jl/v0.9.21/faq/#Is-PythonCall/JuliaCall-thread-safe?).
 
+When starting a Julia REPL with multiple threads, there must be exactly one interactive thread,
+to avoid triggering a segmentation fault on tab completion (issue [#586](https://github.com/JuliaPy/PythonCall.jl/issues/586)).
+Check this with `Threads.nthreads(:interactive)` or `versioninfo()`, set it with `JULIA_NUM_THREADS=X,1`,
+where `X` is the number of default threads, or use the Julia `--threads` CLI flag, see `julia --help`.
+
 Related issues:
 [#201](https://github.com/JuliaPy/PythonCall.jl/issues/201),
 [#202](https://github.com/JuliaPy/PythonCall.jl/issues/202),

docs/src/pythoncall.md

@@ -392,6 +392,8 @@ Both `@unlock` and `@lock` are important. If the GIL were not unlocked, then a d
 would occur when attempting to lock the already-locked GIL from the threads. If the GIL
 were not re-locked, then Python would crash when interacting with it.
 
+With multiple Julia threads you need exactly one interactive thread, see the [FAQ](@ref faq-multi-threading).
+
 You can also use [multi-threading from Python](@ref py-multi-threading).
 
 ### Caveat: Garbage collection

docs/src/releasenotes.md

@@ -1,5 +1,11 @@
 # Release Notes
 
+## 0.9.26 (2025-07-15)
+* Added PySide6 support to the GUI compatibility layer.
+* Added FAQ on interactive threads.
+* Added CI benchmarking suite.
+* Bug fixes.
+
 ## 0.9.25 (2025-05-13)
 * Added `PYTHON_JULIACALL_HEAP_SIZE_HINT` option to configure initial Julia heap size.
 * `Base.elsize` now defined for `PyArray`.

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "juliacall"
-version = "0.9.25"
+version = "0.9.26"
 description = "Julia and Python in seamless harmony"
 readme = { file = "README.md", content-type = "text/markdown" }
 classifiers = [