When using the debugger to call Python via PyCall the return type can be different than when not using the debugger. Here's an MWE where @run gives a different return type:
_ _ _(_)_ | Documentation: https://docs.julialang.org
(_) | (_) (_) |
_ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 1.5.2 (2020-09-23)
_/ |\__'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |
julia> using PyCall
julia> using Debugger
julia> np = pyimport("numpy")
PyObject <module 'numpy' from '/home/me/miniconda3/envs/test-pycall/lib/python3.7/site-packages/numpy/__init__.py'>
julia> np.arange(2)
2-element Array{Int64,1}:
0
1
julia> @run np.arange(2)
PyObject array([0, 1])
julia> versioninfo()
Julia Version 1.5.2
Commit 539f3ce943 (2020-09-23 23:17 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-9.0.1 (ORCJIT, nehalem)
julia> using Pkg
julia> Pkg.status()
Status `~/.julia/environments/v1.5/Project.toml`
[39de3d68] AxisArrays v0.4.3
[336ed68f] CSV v0.7.7
[717857b8] DSP v0.6.8
[a93c6f00] DataFrames v0.21.7
[31a5f54b] Debugger v0.6.6
[7a1cc6ca] FFTW v1.2.4
[5789e2e9] FileIO v1.4.3
[7073ff75] IJulia v1.21.3
[6a3955dd] ImageFiltering v0.6.15
[82e4d734] ImageIO v0.3.0
[6218d12a] ImageMagick v1.1.6
[86fae568] ImageView v0.10.9
[916415d5] Images v0.22.4
[e1d29d7a] Missings v0.4.4
[a15396b6] OnlineStats v1.5.6
[91a5bcdd] Plots v1.6.8
[c3e4b0f8] Pluto v0.11.14
[7f904dfe] PlutoUI v0.6.1
[08abe8d2] PrettyTables v0.9.1
[438e738f] PyCall v1.92.1
[2913bbd2] StatsBase v0.33.1
[ab02a1b2] TableOperations v0.2.1
[bd369af6] Tables v1.0.5
[5e47fb64] TestImages v1.2.3Using Python 3.7.4 and numpy 1.16.5.
When using the debugger to call Python via PyCall the return type can be different than when not using the debugger. Here's an MWE where @run gives a different return type:
Using Python 3.7.4 and numpy 1.16.5.