You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/pythoncall.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -289,6 +289,7 @@ variables.
289
289
|`exe`|`JULIA_PYTHONCALL_EXE`| Path to the Python executable, or special values (see below). |
290
290
|`lib`|`JULIA_PYTHONCALL_LIB`| Path to the Python library (usually inferred automatically). |
291
291
|`pickle`|`JULIA_PYTHONCALL_PICKLE`| Pickle module to use for serialization (`pickle` or `dill`). |
292
+
|`fix_qt_plugin_path=<true\|false>`|`JULIA_PYTHONCALL_FIX_QT_PLUGIN_PATH=<false\|true\|0\|1\|no\|yes>`| When true (the default), automatically [fix the Qt plugin path](@ref`PythonCall.fix_qt_plugin_path`) when activating a Qt-based event loop. |
292
293
293
294
The easiest way to set these preferences is with the
Copy file name to clipboardExpand all lines: src/Compat/gui.jl
+9-32Lines changed: 9 additions & 32 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ This fixes the problem that Qt does not know where to find its `qt.conf` file, b
7
7
always looks relative to `sys.executable`, which can be the Julia executable not the Python
8
8
one when using this package.
9
9
10
-
If `CONFIG.auto_fix_qt_plugin_path` is true, then this is run automatically before `PyQt4`, `PyQt5`, `PySide`, `PySide2` or `PySide6` are imported.
10
+
If the `fix_qt_plugin_path` preference is true, then this is run automatically before `PyQt4`, `PyQt5`, `PySide`, `PySide2` or `PySide6` are imported.
11
11
"""
12
12
functionfix_qt_plugin_path()
13
13
C.CTX.exe_path ===nothing&&returnfalse
@@ -53,30 +53,6 @@ function fix_qt_plugin_path()
53
53
returnfalse
54
54
end
55
55
56
-
# """
57
-
# pyinteract(; force=false, sleep=0.1)
58
-
59
-
# Some Python GUIs can work interactively, meaning the GUI is available but the interactive prompt is returned (e.g. after calling `matplotlib.pyplot.ion()`).
60
-
# To use these from Julia, currently you must manually call `pyinteract()` each time you want to interact.
61
-
62
-
# Internally, this is calling the `PyOS_InputHook` asynchronously. Only one copy is run at a time unless `force` is true.
63
-
64
-
# The asynchronous task waits for `sleep` seconds before calling the hook function.
65
-
# This gives time for the next prompt to be printed and waiting for input.
66
-
# As a result, there will be a small delay before the GUI becomes interactive.
checkpref(::Type{Bool}, x::AbstractString) = x in ("1", "yes", "true") ?true: x in ("0", "no", "false") ?false:error("expecting '0', 'no', 'false', '1', 'yes' or 'true'")
0 commit comments