JuliaPy / JuliaPy/PythonCall.jl

Lazy load CondaPkg (and Pkg), I think LazyModules for that, or better option?

未关闭
#549 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
enhancement
主要语言
Julia
星标
1.1k
派生
86
平均合并
1 天 22 小时
30 天内合并 PR
3

描述

At least when I set:
ENV["JULIA_CONDAPKG_BACKEND"] = "Null"

I get: ERROR: InitError: CondaPkg is using the Null backend but Python is not installed

though, so not investigating further (I have Python installed).

With this one loads but not any faster (but should too):
```
ENV["JULIA_PYTHONCALL_EXE"] = "@PyCall" # optional

julia> ENV["JULIA_PYTHONCALL_EXE"] ="/usr/local/bin/python3";

julia> @time using PythonCall
┌ Warning: Python library "/usr/local/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.a" could not be opened.
└ @ PythonCall.C ~/.julia/dev/PythonCall/src/C/context.jl:122
┌ Warning: Python library "/usr/local/lib/libpython3.12.a" could not be opened.
└ @ PythonCall.C ~/.julia/dev/PythonCall/src/C/context.jl:122
ERROR: InitError: Could not find Python library for Python executable "/usr/local/bin/python3".

If you know where the library is, set environment variable 'JULIA_PYTHONCALL_LIB' to its path.
```

贡献指南

这个仓库没有索引到贡献指南

调研方向

Start by reproducing the CondaPkg Null-backend error and the PythonCall initialization failure described in the issue, then inspect how CondaPkg and Pkg are loaded. The referenced warning originates at ~/.julia/dev/PythonCall/src/C/context.jl:122; done should mean startup no longer eagerly loads these dependencies while the configured Python backends still initialize correctly.

由索引模型根据 Issue 内容生成。

评估

技术栈
julia, python
领域
performance
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。